The package has no declared or detected license and the repository provides no security policy. Its README and organization-backed, name-matching repository help, but the project offers little evidence of current support.
38%
Total Score
50
100
70
83
The last release was about 10 years ago, with no releases in the past 12 months and only three releases overall. This is strong evidence of abandonment for a dependency consumers may need to maintain.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and leaving no evidence of ongoing maintenance.
Neither the package metadata, artifact, nor repository has a detected license or license file. That creates a material adoption and redistribution problem.
The linked repository has no security policy. For an old web application skeleton, this reduces transparency about vulnerability reporting and maintenance expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
iplox/iplox Version 0.1.* | — | — |
smarty/smarty Version 3.* | — | — |
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.