vormkracht10/oauth2-genesys
The repository has recent maintenance evidence, tests, and dependency scanning, but its workflow safeguards need tightening and it has no published security policy. The single registry publisher is less concerning because the source repository is organization-owned and matches the package.
64%
Total Score
75
88
67
Health Score Breakdown
The latest registry release was over two years ago, with no releases in the last 12 months; this is a meaningful maintenance concern even though the repository was pushed more recently.
There were no commits and no active maintainers in the last three months, limiting evidence of continuing development despite the repository's recent push timestamp.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
v0.2.4 is not a stable-major release, so compatibility expectations are lower for consumers depending on this package.
All 11 action references are unpinned, and the audit found high-confidence bot-condition and unpinned-image issues; the pull_request_target workflow has no untrusted checkout or script-injection sink, limiting the risk to workflow hygiene rather than a severe dependency-health failure.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Bas van Dinther |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 mockery/mockery Version ^1.5 | — | — |
league/oauth2-client Version ^2.6 | — | — |
league/oauth2-server Version ^8.3 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 3 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.