Recent releases, tests, documentation, and clear licensing support adoption. The project is young, and its automated checks rely on unpinned actions without a dedicated security policy.
68%
Total Score
83
100
86
83
All 13 recent commits came from one contributor, leaving maintenance highly concentrated; organization ownership provides some handoff capacity but does not remove the current single-contributor risk.
Composer build tooling is present, but no security-scanning tooling was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users lack a documented reporting and response path if dependency or integration problems are found.
Version 0.2.0 is not yet a stable major release, so its API and behavior may still change as the young project matures.
Both workflows use read-only permissions and the audit found no dangerous triggers, untrusted checkouts, script injection, or other findings. However, all three referenced actions are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
pushinbr/pam-native Version ^0.8.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.