The repository has no security policy or security-scanning tools, and its single registry maintainer offers limited resilience. The matching repository, MIT license, README, and no install scripts provide useful transparency.
43%
Total Score
25
81
83
The latest release was published in April 2018, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency whose compatibility may need ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating no current maintenance capacity.
Only one account has registry publish access. The repository owner is an individual rather than an organization, so there is little visible redundancy in publishing or maintenance capacity.
Composer build tooling is present, but no security-scanning tools were detected. The missing security automation adds a modest maintenance concern, though it does not by itself make the package unfit.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a meaningful transparency and maintenance gap for a library used in applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version >=1.6 | — | — |
google/apiclient Version ^2.0 | — | — |
symfony/twig-bundle Version >=2.0 | — | — |
symfony/framework-bundle Version >=2.3 | — | — |
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.