gmazzap/reject-notify
The MIT license, README, and tiny dependency surface make inspection straightforward. The repository does not name the package in its README and has no security policy, adding transparency concerns for a lone maintainer.
32%
Total Score
0
100
63
75
Health Score Breakdown
The package has only one release, published over 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for many years.
The repository is not marked archived, but its last push was over 11 years ago. The stale activity still indicates serious maintenance risk.
The repository name does not match the package name and its README does not mention the package. Although this may be a naming convention, it makes package-to-source ownership less transparent.
Composer is used as a build tool, but no security-scanning tooling is present. This is a modest transparency and maintenance gap, not a severe risk by itself.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Giuseppe Mazzapica |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 11 years ago
- Created
- 11 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.