Yammer authentication strategy for Opauth
38%
Total Score
unhealthy
Risky: a single 2014 release and no subsequent maintenance make this a poor dependency choice.
This is the only release, published over 12 years ago, with no releases in the last 12 months. That strongly raises abandonment risk, and the repository's matching last push provides no compensating maintenance evidence.
The repository is not archived, which keeps it technically available, but its last push was over 12 years ago and does not offset the stale release history.
The repository has no security policy, leaving no documented channel or process for handling security reports. The package's age and lack of maintenance make this gap more significant.
The latest version is v0.1.0 and is not a stable major release, which indicates limited maturity. The clear README and focused package scope partly reduce the practical impact of this immaturity.
No GitHub Actions workflows were found, so there are no workflow risks to assess. This also means the repository provides no automated workflow-based verification evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
opauth/opauth Version >=0.4.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.