The MIT license, usable README, and clean package layout support straightforward adoption. Repository security tooling and an explicit security policy are absent, leaving limited visible oversight for future changes.
58%
Total Score
50
88
88
The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to offset the thin maintenance history. This is a modest capacity concern, not proof of abandonment.
This package has only one release, published about 17 months ago, with no releases in the last 12 months. That provides little evidence of sustained maintenance for a data dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no activity since the initial release. This materially raises abandonment and freshness concerns.
Composer build tooling is present, but no security scanning tools were detected. For a small data package this is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. That limits guidance for reporting problems, though the package's small data-focused scope makes this a minor concern.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.