Risky to adopt for a new project: the latest release was over 11 years ago and the repository has had no recent commits. It is licensed, documented, and not deprecated, but the long inactivity makes ongoing compatibility and maintenance unlikely.
42%
Total Score
50
75
75
The latest release was published over 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility updates.
There were no commits and no active maintainers in the last 3 months, consistent with the release history showing that maintenance has effectively stopped.
There were no new or closed issues or pull requests in the last month, while two issues remain open. This suggests little ongoing support for users.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap, though the repository contains no workflows that would add a separate automation risk.
The repository is not archived, but its last push was over 10 years ago. The unarchived status does not compensate for that observed inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/nette Version >=2.1.0,<2.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.