The package has clear documentation, tests, a license, and organization backing. Its release burst was concentrated in five days, with no commits or active maintainers in the past three months, while the workflow uses broad write access and unpinned actions.
58%
Total Score
50
100
86
75
There were zero commits and zero active maintainers in the past three months. For a package only 202 days old, that is a meaningful sign that maintenance may have stopped after its initial release burst.
All 8 releases arrived within a concentrated five-day period, which shows initial activity but provides little evidence of sustained maintenance over the package's 202-day age.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe dependency risk.
The repository has no security policy. This limits reporting transparency, though the package is a small data and lookup library with no other provided security signal indicating severe risk.
The only workflow was fully analyzed and had no detected sinks or audit findings, but it grants top-level write access and leaves both action references unpinned. Those are workflow hygiene weaknesses without an untrusted trigger or sink to make them severe.
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.