The package is clearly licensed, has a usable README, and is backed by an organization. Its repository does not identify the package in its README, and it has no security scanning, leaving ownership and maintenance less clear.
48%
Total Score
50
71
83
Only three releases exist, with none in the last 12 months; the latest release was published over four years ago. This is strong evidence of abandonment risk, though the package is not marked deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided signal shows recent maintenance to offset this.
The repository name does not match the package name and its README does not mention the package, so the repository’s ownership of this release is less clear. The organization backing provides some context but does not resolve the mismatch.
Composer build tooling is present, but no security scanning tools were detected. The build setup is a small positive, while the missing scanning is a minor hygiene gap.
The repository has no security policy. This is a transparency and maintenance gap, although it is less serious than the absence of recent release and commit activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^4.4|^5.0 | — | — |
symfony/http-kernel Version ^4.4|^5.0 | — | — |
symfony/framework-bundle Version ^4.4|^5.0 | — | — |
idmarinas/lotgd-contracts Version ^0.2.0 | — | — |
symfony/dependency-injection Version ^4.4|^5.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.