Please add a security policy
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 37
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Please add a SECURITY or SECURITY.md file to the distribution and root directory of the git repo that explains how to report a security vulnerability.
CPANSec has a guide for adding a security policy [1] and also links to software to generate security policies when you rebuild a distribution for release.
You can enable private vulnerability reporting in your GitHub repository [2]. This allows people to create private issues for security vulnerabilities, and lets your collaborators work on private forks. (GitHub also treats security policies as "first class" files along with the README and LICENSE files.)
[1] https://security.metacpan.org/docs/guides/security-policy-for-authors.html
Note: this issue is part of a project by CPANSec to encourage popular CPAN distributions to add a security policy.
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
Read the CPANSec security-policy guide and the repository's distribution setup first. Add a SECURITY or SECURITY.md file at the repository root and ensure it is included in the distribution; done means it clearly explains how to report a security vulnerability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100