The package is clearly licensed, has repository tests, and uses no install-time scripts. Recent registry releases and an active, unarchived project help, but no commits in three months and no security scanning leave maintenance evidence thin.
68%
Total Score
75
100
93
75
The repository recorded zero commits and zero active maintainers during the last three months. This weakens evidence of ongoing maintenance, although the recent release shows the project has not been abandoned outright.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene weakness rather than evidence that the release is unsafe.
The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, but it is not by itself evidence of abandonment.
No GitHub Actions workflows were present, so there were no workflow hazards or unpinned actions to flag. This also means there is no observed workflow automation supporting the build or release process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nelexa/zip Version ^4.0 | — | — |
greenter/core Version ^5.0 | — | — |
greenter/gre-api Version ^1.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.