Tests, a clear MIT license, and no install-time scripts reduce packaging risk. Organization backing and a repository matching the package improve provenance, but the missing security policy limits transparency.
38%
Total Score
50
71
75
The package has only one release, published more than 8 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a package intended as a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, while its last push was more than 8 years ago. This directly supports a strong abandonment concern.
Composer is used as a build tool, but no security-scanning tooling was found. That is a transparency and maintenance weakness, though it is secondary to the much older activity gap.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a transparency concern for a dependency.
Version 0.0.1 is the only release and is not a stable major version, leaving little evidence of a mature compatibility track. Its non-prerelease status provides only limited reassurance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^4.0 | — | — |
symfony/config Version ^4.0 | — | — |
symfony/dotenv Version ^4.0 | — | — |
symfony/finder Version ^4.0 | — | — |
monolog/monolog Version ^1.23 | — | — |
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.