Documentation, tests, and matching source make the package straightforward to evaluate. A small publishing base and absent security policy leave less resilience if the upstream service or code needs attention.
64%
Total Score
50
100
88
50
The registry namespace and repository are owned by the same individual account. This supports ownership continuity, but it does not provide the resilience of an organization-backed project.
The package has 10 releases since August 2014, but none in the last 12 months; its latest release was in May 2024. This indicates stalled release activity for a package developers may still depend on.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this is evidence of limited current maintenance.
The project uses Make and Composer, showing basic build tooling, but no security-scanning tools were detected. That is a modest transparency and maintenance gap, not a severe risk on its own.
The repository has no security policy. For a small wrapper around an external service this is a transparency gap, although it does not by itself indicate abandonment or unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/utils Version ^3.0 | — | — |
nette/caching 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.