The repository has tests, release notes, and a matching organizational home. Its tiny audience, absent security policy, and loosely pinned workflow reduce confidence for long-term use.
62%
Total Score
75
83
50
The package has 10 releases over nearly 10 years, but none in the last 12 months; its latest release was about 18 months ago. This indicates a slow and currently inactive release cadence.
There were no commits and no active maintainers in the last 3 months, consistent with the long gap since the latest release. This is meaningful evidence of currently inactive maintenance.
The repository has only 4 stars and 2 forks, showing a small user and contributor ecosystem. Popularity is supporting evidence, but this modest adoption lowers confidence in outside scrutiny.
The project uses Make and Composer, but no security scanning tools were detected. The missing scanning is a hygiene gap, not a severe risk by itself.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This reduces transparency for a package intended for project dependencies.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/tester Version ^2.4.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.