Its long history, frequent releases, stable versioning, and substantial source tree support continued use. The small audience, absent security policy and scanning, and no active contributors in the last three months leave meaningful maintenance and transparency concerns.
68%
Total Score
75
100
83
83
There were no commits and no active maintainers in the last three months. Although a release was published during that period, the absence of development activity is a maintenance concern.
The repository name does not match the package name and its README does not mention ns/ace-bundle. That makes the package-to-source relationship harder to verify and raises a provenance concern.
The repository has 1 star and 2 forks, indicating a small user and contributor audience. Popularity is supporting evidence only, so this lowers confidence in external maintenance capacity rather than making the package unfit.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a transparency and hygiene gap, not evidence of maliciousness.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^2.0|^3.0 | — | — |
doctrine/orm Version ^2.0|^3.0 | — | — |
symfony/form Version ^6.0|^7.0 | — | — |
symfony/routing Version ^6.0|^7.0 | — | — |
symfony/security-core Version ^6.0|^7.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.