The package has a clear README and matching repository, but its lone maintainer has not published a release since September 2015 and the repository shows no commits in the last three months. Two open issues and no security policy leave little evidence of active support.
40%
Total Score
33
83
75
The latest release was published in September 2015, with no releases in the last 12 months. That long gap is strong evidence of abandonment risk for a framework integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the stale release history and showing no current maintenance activity.
The package has one registry maintainer, and the project is backed by an individual repository owner rather than an organization. A single maintainer increases continuity risk when activity is already absent.
Two issues and one pull request remain open, with no issues or pull requests closed in the last month. This reinforces the lack of visible project activity.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is less significant than the project's inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/nette Version ~2.1 | — | — |
opauth/google Version * | — | — |
opauth/opauth Version * | — | — |
opauth/twitter Version * | — | — |
opauth/facebook Version * | — | — |
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.