Dropbox strategy for Opauth
42%
Total Score
unhealthy
Risky: no repository activity for more than 11 years, with a single maintainer and no security tooling.
The package has had no release in more than 11 years and only three releases overall, which is strong evidence of abandonment for an integration package.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long gap since its final release.
One registry maintainer is a limited publishing base; the linked project is user-owned, so there is no organization backing shown to compensate for that concentration.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but these figures provide no supporting evidence of active community maintenance.
Composer is used for builds, but no security-scanning tool is present, leaving dependency and release hygiene less independently checked.
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.