putio/frontend-docs
Structure and rewrite docs for frontend repositories, especially README.md, CONTRIBUTING.md, SECURITY.md, and other top-level docs. Use when creating or reorganizing frontend repo docs, clarifying user vs contributor guidance, reducing doc sprawl, or fixing stale commands, paths, and links in top-level docs.
95
Quality
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Securityby
Passed
No known issues
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
- avoid destructive behavior, service disruption, or automated high-volume testing
- do not attempt social engineering, physical attacks, or denial-of-service testing
## Supported Versions
Describe the repo's actual support policy here. If the repo does not have a formal version-support policy, say so plainly instead of guessing.
## 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.