jeremylivingston/exfoliate
Usable with caveats: the package is clearly identified, licensed, tested, and has no install-time scripts, but its latest release was about 10 years ago and repository activity stopped about 5 years ago. Expect limited maintenance and verify compatibility before adopting it.
55%
Total Score
63
100
78
90
Health Score Breakdown
One registry maintainer is consistent with this individually owned project, but it leaves little redundancy if the owner becomes unavailable.
The registry namespace and repository owner match, and the owner is an individual, providing direct ownership alignment but no organizational backing or maintainer redundancy.
Only two releases exist, with none in the last 12 months; the latest release was about 10 years ago. This is a substantial maintenance and compatibility concern despite the package's stable version.
There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this indicates the project is largely inactive.
The repository has only 2 stars and 2 forks, indicating limited adoption and external support. Popularity is supporting evidence rather than a decisive health verdict, so this is a minor concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jeremy Livingston |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 13 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.