regenerate
The MIT license, npm provenance, clear README, and repository tests support dependable adoption. Type declarations and a security policy are absent, while workflow references are unpinned and one workflow installs an ad hoc package; these are manageable hygiene concerns.
82%
Total Score
70
89
67
100
Health Score Breakdown
Only one registry account has publish access, creating publishing concentration, but registry access records do not by themselves establish whether repository maintenance is active.
The repository is owned by an individual rather than an organization, so there is no organizational handoff capacity to offset the concentrated recent contribution pattern.
One contributor made 80% of the five recent commits, but a second contributor remains active, so the concentration is a moderate resilience concern rather than a severe abandonment risk.
The repository reports no build tool and no security-scanning tooling, leaving less automated protection than mature projects commonly provide.
No repository security policy was found, making the reporting path for vulnerabilities less transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 13 years ago
- Unpacked Size
- 0.1 MB
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.