A single maintainer and no commits in the last three months reduce maintenance resilience. The package is well documented, tested, licensed, and recently released, but its workflow uses three unpinned actions and has no security scanning.
68%
Total Score
50
100
94
75
Only one registry account has publishing access, creating single-person publishing and continuity risk; the individual repository ownership is consistent with that model but does not add redundancy.
There were no commits and no active maintainers in the last three months. The recent release partly offsets this, but the lack of current development activity lowers maintenance confidence.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-hygiene gap without indicating maliciousness.
The repository has no security policy, which makes vulnerability reporting and response expectations less transparent.
The sole workflow was fully analyzed with no dangerous triggers or audit findings, but all three referenced actions are unpinned, reducing build reproducibility and update integrity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^3.0 || ^4.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.