The package is clearly licensed, has a readable artifact, and uses no install-time scripts. Its repository does not identify the package in its README, adding uncertainty about project ownership.
30%
Total Score
0
100
71
75
There has been only one release, published about 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package intended to be maintained as a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap. No provided maintenance signal compensates for this inactivity.
The repository name does not match the package name and its README does not mention the package, so the repository's relationship to this release is not clearly established. This adds transparency and ownership risk.
Composer is used as the build tool, but no security scanning tooling is present. This is a modest hygiene gap and does not by itself establish that the release is unsafe.
The repository has no security policy. For a small, inactive project this weakens vulnerability-reporting transparency, though it is secondary to the much stronger maintenance concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/doctrine-bundle Version ~1.2 | — | — |
symfony/framework-bundle Version ~2.1 | — | — |
doctrine/doctrine-fixtures-bundle Version 2.2.* | — | — |
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.