A single maintainer and no commits in about nine months limit confidence in ongoing maintenance. The repository has tests, release notes, dependency scanning, and clear licensing, but workflow credential handling and unpinned actions add avoidable supply-chain exposure.
55%
Total Score
67
100
86
75
Only one registry account has publish access, which limits publishing redundancy; the organization-backed repository provides some compensating project ownership context.
The package has only two releases over about 14 months, with one release in the last 12 months; this suggests a small and relatively slow-moving project, though it is not abandoned by release history alone.
There were no commits and no active maintainers in the last three months, a meaningful sign that maintenance may have slowed.
No security policy is provided, leaving vulnerability reporting guidance unclear for consumers and contributors.
Version v0.2.0 is not a prerelease, but the package remains below a stable major version and has a very short release history, so compatibility maturity is limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
beberlei/assert Version ^3.3 | — | — |
symfony/console Version ^5.4 || ^6.0 || ^7.0 | — | — |
nikolaposa/version Version ^4.1.1 | — | — |
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.