The small codebase has clear usage documentation, a focused runtime dependency, and organization backing. Maintenance appears dormant, with no recent commits or releases, while the absence of tests and security scanning limits assurance.
58%
Total Score
50
100
79
75
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long release gap, this is meaningful evidence of dormant maintenance.
The package has only two releases across more than ten years, with no release in about two and a half years. This indicates a slow and currently inactive release cadence, though the package may be intentionally stable.
Composer is used for builds, which fits the ecosystem, but no security scanning tools are configured. That is a modest transparency and assurance gap rather than evidence of unsafe behavior.
The repository has no security policy. For a small templating integration this is not severe, but it leaves vulnerability-reporting expectations and response processes unclear.
Version v0.1.1 is not a prerelease, but it remains below a stable major version. The absence of recent releases makes its maturity harder to establish.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
smarty/smarty Version * | — | — |
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.