wenhao26/pepper
MIT licensing, a matching repository, release notes, and a small dependency surface improve transparency. Limited project oversight means future fixes and security response are uncertain.
58%
Total Score
50
100
86
75
Health Score Breakdown
The package has only one release, published about 2 years and 10 months ago, with no releases in the last 12 months. This is a meaningful maintenance concern, though the release is stable rather than experimental.
The repository had no commits and no active maintainers in the last 3 months, consistent with the last push occurring about 2 years and 10 months ago. This reinforces the concern that fixes may not arrive promptly.
Composer is used for the build, but no security scanning tool is configured. For a small package this is a modest oversight gap rather than evidence of unsafe behavior.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This lowers transparency and response confidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Pepper |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.