yarkhan/cnpjdf
The MIT license, clear README, and package-repository name match provide useful transparency. The repository has no security policy or scanning, while its lone maintainer has not committed in over nine years.
43%
Total Score
33
75
88
Health Score Breakdown
This is the package's only release, published over nine years ago, with no releases in the last 12 months. That strongly suggests abandonment risk.
There were zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases and indicating serious abandonment risk.
Only one registry maintainer is listed. That is a thin publishing base and leaves little visible redundancy if the maintainer stops supporting the package.
The repository is owned by an individual rather than an organization, so the single-maintainer concern is not offset by visible organizational backing.
Composer is used for the build, which is appropriate for a Packagist package, but no security-scanning tools are present.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Yarkhan |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.