putio/frontend-repos
Set up put.io frontend repos: README/CONTRIBUTING/SECURITY, CI, package scripts, verify commands, release workflows, deploy pipelines, test harnesses, and publish/deploy flows. Use for repo setup, repo cleanup, project setup, configuring CI or deployment, or making a package/app/SDK repo documented, verifiable, and deliverable. Skip feature code, SDK API work, Vite+ migrations, and self-verification.
75
Quality
94%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Securityby
Passed
No known issues
docs-security-template.mdreferences/
Frontend SECURITY.md Template
Use this as a starting point for frontend repos. Adapt the scope and supported-version wording to the repo, but keep the document short and private-first.
# Security
If you believe you have found a security or privacy issue in this project, please report it privately.
## Contact
- email: devs@put.io
Private reports are preferred for security and privacy issues.
If you are unsure whether something is sensitive, email first instead of opening a public issue.
## Scope
Useful reports usually include issues involving:
- authentication, authorization, or session handling
- token, secret, or credential exposure
- cross-site scripting, request forgery, or injection
- privilege escalation or access-control bypass
- private or user data exposure
## Guidelines
- test only against accounts, environments, and data you control
- keep testing non-destructive, low-volume, and service-safe
- limit reports to technical vulnerabilities in this project
## Supported Versions
Describe the repo's actual support policy here. If the repo has no formal version-support policy, say so plainly.
## Disclosure
Please allow a reasonable amount of time to investigate and fix the issue before sharing details publicly.
If the report is valid, we will work on a fix and coordinate disclosure as appropriate.