Clear documentation, tests, release notes, and recent commits support dependable maintenance. The project still relies on one active contributor, lacks a security policy, and leaves half of workflow action references unpinned.
78%
Total Score
75
100
94
75
The package and repository are owned by the same individual, so the single-person maintainer base is not offset by organization backing.
All four recent commits came from one contributor, leaving maintenance dependent on a single person and increasing abandonment risk.
Composer build tooling is used, but no security-scanning tooling was detected; the missing scanner is a maintenance hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Both workflows scope permissions at job level and have no untrusted checkouts or injection findings, but 4 of 8 action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
yahnis-elsts/plugin-update-checker Version ^5.6 | — | — |
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.