Yinxiang strategy for Opauth
32%
Total Score
0
57
75
The package has had no release in more than 11 years, with zero releases in the last 12 months. This is strong evidence of abandonment for a dependency intended for ongoing use.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and increasing abandonment risk.
The repository name does not match the package name and its README does not mention opauth/yinxiang. That makes package ownership and source provenance unclear rather than merely reflecting a normal subpackage layout.
The manifest declares MIT, but the only detected license file is Apache-2.0 under Vendor/tmhOAuth. This licensing mismatch creates real adoption and compliance uncertainty.
The repository uses Composer for builds, providing basic project structure, but it has no security-scanning tooling. For this small, inactive project, that leaves a modest transparency and maintenance 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.