xervice/github-oauth
The package has a useful README, tests, an MIT declaration, and organization backing. It lacks security scanning and a security policy, leaving maintenance and security transparency weaker than its basic packaging suggests.
38%
Total Score
50
67
50
Health Score Breakdown
The latest release was published about eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency at version 3.0.0.
The repository has recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap and indicating no visible ongoing maintenance.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little additional confidence in long-term support.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance hygiene gap, though not severe on its own.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a transparency concern for a package involved in OAuth integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mike Bertram |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 xervice/core Version ^4.0.0 | — | — |
xervice/user Version ^2.0.0 | — | — |
propel/propel Version 2.0.0-alpha8 | — | — |
xervice/logger Version ^2.0.0 | — | — |
guzzlehttp/guzzle Version ^6.3.3 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.