Amazon strategy for Opauth
38%
Total Score
unhealthy
Risky: a single release from 2014, no recent commits, and no security policy make long-term support uncertain.
The package has only one release, published in July 2014, with no releases in the last 12 months. This is strong evidence of a largely inactive dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no current maintenance capacity.
The repository has zero stars and forks and one watcher, providing little supporting evidence of community review or adoption. Popularity is only supporting evidence, so this reinforces rather than determines the result.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap rather than evidence of unsafe behavior by itself.
The repository has no security policy. For an authentication integration, this is a meaningful transparency and vulnerability-reporting gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
opauth/opauth Version >=0.2.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.