The organization-backed repository matches the package and provides release notes for this version, but it has no security scanning. Licensing is also not declared or detected, which makes adoption and redistribution less transparent.
52%
Total Score
75
81
100
Neither the package nor the linked repository has a declared or detected license file. That creates a real transparency and redistribution concern for a dependency.
The latest release was about 4 years and 7 months ago, with no releases in the last 12 months. This is strong evidence of an aging project, despite its 16-release history.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long gap since the latest release. This raises maintenance and abandonment concerns.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest process gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ~1.18 | — | — |
evaneos/berthe Version ~5.0 || ^6.0 | — | — |
evaneos/pyrite Version ^5.0.0 | — | — |
league/fractal Version ~0.7.0 | — | — |
monolog/monolog Version ^1.13 | — | — |
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.