get-package-info
Gets properties from package.json files in parent directories.
42%
Total Score
unhealthy
No registry release since 2016 and no recent repository commits point to a largely inactive project.
Health Score Breakdown
The latest release was in October 2016, about 9 years and 11 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package's six historical releases.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, confirming that current maintenance activity is absent.
No build attestation or trusted-publisher provenance is present. This weakens publication transparency, but it is not by itself evidence that the release is unsafe.
Only one registry publishing account is listed. This is a thin operational base for an independently owned project and increases continuity risk, although registry access does not prove who contributes code.
The repository has no security policy. That is a transparency and vulnerability-reporting gap, though it is secondary to the much stronger inactivity evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 debug Version ^2.2.0 | — | — |
bluebird Version ^3.1.1 | — | — |
lodash.get Version ^4.0.0 | — | — |
read-pkg-up Version ^2.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.