Several examples expose some internal files via static assets
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
I have found several examples that expose some internal files via static files. I think this should be fixed to avoid having users build on these templates and unknowingly expose sensitive files.
template: https://vercel.com/templates/hono/hono-on-vercel
https://hono-starter.vercel.sh/package-lock.json
https://hono-starter.vercel.sh/README.md
https://hono-starter.vercel.sh/tsconfig.json
template: https://vercel.com/templates/python/python-hello-world
https://python-hello-world.vercel.app/README.md
template: https://vercel.com/templates/other/nodejs-serverless-function-express
https://nodejs-api-example.vercel.app/README.md
template: https://vercel.com/templates/other/fastify-serverless-function
https://fastify-example.vercel.app/pnpm-lock.yaml
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Hono, Python Hello World, Node.js Express, and Fastify example templates linked in the issue, then reproduce the listed URLs. Identify how each example exposes README, lock, or TypeScript configuration files through static assets. Done means the listed internal files are no longer publicly served for every affected template, with the URLs checked again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, node.js, python, typescript
- Domain
- security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100