The package is small and clearly identified, with a matching repository, license, README, and release notes. Maintenance has been inactive for about 2 years and 8 months, while the repository has no tests, security scanning, or security policy.
62%
Total Score
50
100
88
83
The registry namespace and repository owner match, but ownership is an individual account rather than an organization. This provides direct identity consistency but limited visible backing capacity.
The package has four releases since December 2018, but none in the past 12 months and the latest release was about 2 years and 8 months ago. This indicates limited ongoing maintenance for a dependency.
The repository recorded zero commits and zero active maintainers in the past 3 months, consistent with the long gap since the last release. This is a meaningful abandonment concern, though the package is small and stable.
Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. For a small template extension this is a transparency and response-process gap, but it is not severe by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^2.0|^3.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.