The package has had no release or commit activity for over four years, and the linked repository has no security policy. Its MIT license, documentation, tests in the repository, and changelog provide useful transparency, but unpinned workflow actions add hygiene risk.
45%
Total Score
25
100
67
75
The latest release was over four years ago, with zero releases in the last 12 months; this is strong evidence of abandonment risk for a library dependency.
There were zero commits and zero active maintainers in the last three months, consistent with the registry's four-year release gap and indicating substantial abandonment risk.
The repository is owned by an individual account rather than an organization, and no organizational backing is shown; combined with inactivity, this leaves limited visible maintenance capacity.
The repository name does not match the package name, but its README explicitly mentions the package, partly compensating for the mismatch while leaving provenance less clear than a direct repository match.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful external backing signal.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/cache Version ^3.1 || ^4.0 || ^5.0 || ^6.0 | — | — |
evenement/evenement Version ^3.0 || ^2.0 || ^1.0 | — | — |
alchemy/binary-driver Version ^1.5 || ~2.0.0 || ^5.0 | — | — |
neutron/temporary-filesystem Version ^2.1.1 || ^3.0 | — | — |
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.