shiniv/sanitize
Its dependency surface is minimal and the package has a matching source tree. However, the lack of licensing and project safeguards makes long-term adoption difficult.
35%
Total Score
0
100
63
50
Health Score Breakdown
There has been only one release, published in October 2017, with no releases in the last nine years. This is strong evidence of abandonment risk for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push in October 2017. No provided signal compensates for this prolonged inactivity.
No license declaration or license file was found in the package or repository. That creates a concrete adoption and redistribution concern.
The package includes a README and has a GitHub release for this version, but it has no tests or changelog. The short README and absent tests reduce transparency for a library consumers must integrate.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these numbers provide no community signal to offset the inactivity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 shiniv |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.