Testing and release notes are present, with clear organizational ownership. The six-month pause in commits and absent security tooling make long-term maintenance less certain.
68%
Total Score
83
100
89
50
The package is about one year old with four releases, all within the last 12 months. Releases were concentrated early, so this supports initial activity but does not establish sustained maintenance.
The repository recorded no commits and no active maintainers during the last three months. With roughly six months since the latest release, this is a meaningful maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
No GitHub Actions workflows were present, so there were no workflow risks to audit. This also provides no automated CI or release hygiene evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spiral/boot Version ^3.15 | — | — |
spiral/files Version ^3.15 | — | — |
symfony/yaml Version ^7.2 || ^8.0 | — | — |
cocur/slugify Version ^4.6 | — | — |
spiral/config Version ^3.15 | — | — |
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.