The package has a clear consumer path and a small implementation. Releases are sparse, no commits were recorded in the last three months, and both workflow actions are unpinned. Tests and a matching README provide useful support.
68%
Total Score
50
100
83
83
The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it offers less visible institutional backing for long-term maintenance.
Only two releases have appeared over roughly 836 days, with a median interval of about 724 days. A release in the last 12 months shows the project is not abandoned, but maintenance is infrequent.
No commits and no active maintainers were recorded during the last three months. The recent release and push partly offset this, but the absence of ongoing activity still raises maintenance concern.
The repository has no stars or forks and one watcher. This provides little community validation, although popularity is only supporting evidence for a small package.
Composer build tooling is present, but no security scanning tools were detected. The missing scanner is a hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^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.