The package includes a useful README, tests, an MIT license, and no registry deprecation. Its workflow uses two unpinned actions, and the repository has no security policy or scanning, adding maintenance and build-hygiene concerns.
42%
Total Score
0
70
50
The latest release was published in August 2017, with no releases in the last 12 months. That long release gap is strong evidence of abandonment risk for a dependency.
There were 0 commits and 0 active maintainers in the last 3 months, while the last repository push was nearly 6 years ago. This indicates sustained inactivity rather than a brief pause.
Composer is used for builds, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap, not a standalone adoption blocker.
The repository has no security policy and no security policy source was detected. This weakens the project's vulnerability-reporting transparency, especially alongside its inactive maintenance.
The single workflow was fully analyzed with no audit findings or untrusted triggers, but both of its two action references are unpinned. That leaves avoidable build reproducibility and action-update risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/extensions Version ~1.1 | — | — |
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.