mr-jiawen/analysis
A single registry maintainer, no security scanning, and no tests leave limited evidence of ongoing care. The MIT license, matching repository, and stable release reduce adoption friction but do not offset the long inactivity.
45%
Total Score
50
79
50
Health Score Breakdown
The package has had only two releases, both in November 2017, with no releases in the last 12 months and roughly eight years since the latest release. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since November 2017.
Only one registry account has publish access. The organization-owned repository provides some backing context, but the observed publishing base remains thin.
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and maintenance gap, though it is less serious than the prolonged inactivity.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a modest transparency concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 chenjiawen |
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.