# guzzle/oauth-subscriber — health index 34/100 (At risk)

> Inspection of the public repository guzzle/oauth-subscriber by inspect.software. It holds a health index of 34 out of 100, placing it in the At risk band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/guzzle/oauth-subscriber
- Report page: https://inspect.software/software/guzzle/oauth-subscriber
- Full JSON report: https://inspect.software/api/repositories/guzzle/oauth-subscriber/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/g/guzzle/oauth-subscriber.svg
- Inspected: 2026-07-20
- Methodology: metrics 1.13.0, report schema 0.16.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 78/100 | Good |
| Community & Adoption | 18% | 79/100 | Good |
| Sustainability & Governance | 24% | 68/100 | Moderate |
| Engineering Quality | 20% | 74/100 | Good |
| Security | 16% | 39/100 | At risk |
| AI Readiness | not counted | 70/100 | Good |

High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At risk ceiling of 49.

## Repository facts

| Field | Value |
|---|---|
| Description | Signs Guzzle requests using OAuth 1.0 |
| Primary language | PHP |
| License | MIT |
| Stars | 240 |
| Forks | 88 |
| Created | 2014-02-28 |
| Last push | 2026-07-20 |
| Latest release | 1.0.0 |
| Commits (last year) | 67 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| packagist | guzzlehttp/oauth-subscriber | 1.0.0 | 349,322 |

## Vitality — 78/100 (Good)

Is the project alive — is code being written and are releases shipping? Weight: 22% of the overall index.

### Development activity — 69/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | partial | 6.2 / 36 | 9/52 weeks with commits |
| Commit volume | partial | 16.5 / 18 | 67 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10 |

### Release discipline — 92/100 (Excellent)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 14 releases published |
| Release recency | met | 36 / 36 | latest release 0 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~62.2 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | maintenance record not established from the collected data |

## Community & Adoption — 79/100 (Good)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 18% of the overall index.

### Popularity & adoption — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 38.6 / 60 | 240 stars |
| Forks | partial | 16.2 / 25 | 88 forks |
| Watchers | partial | 5.6 / 15 | 11 watchers |

### Community health — 93/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (MIT) |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | met | 7.2 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

### Ecosystem adoption (downloads) — 89/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 73.9 / 80 | 349,322 downloads/month across packagist |
| Registry dependents | partial | 14.8 / 20 | 164 packages depend on it |

## Sustainability & Governance — 68/100 (Moderate)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% of the overall index.

### Maintainer resilience (bus factor) — 42/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 10 / 22.5 | top contributor authored 56% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 20 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 28 contributing companies or organizations |

### Issue & PR responsiveness — 75/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | met | 46.8 / 46.8 | 100% of issues closed |
| PR acceptance | partial | 28.3 / 38.2 | 85/115 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 66/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 14.7 / 25 | 110 followers of guzzle |
| Track record | partial | 21.5 / 25 | 19 public repos, account ~15 yr old |

### Package maintenance — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on packagist |
| Publish recency | met | 35 / 35 | latest publish 0 days ago |
| Version history | met | 20 / 20 | 19 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 74/100 (Good)

Are baseline engineering and documentation practices in place? Weight: 20% of the overall index.

### Engineering practices — 80/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 2 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .php-cs-fixer.dist.php |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | partial | 16 / 20 | 17 out of 20 merged PRs checked by a CI test -- score normalized to 8 |

### Documentation — 65/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | not met | 0 / 10 | — |

## Security — 39/100 (At risk)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 24/100 (Critical)

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier to Security posture and gives it an At risk ceiling of 49.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | partial | 2 / 2.5 | 17 out of 20 merged PRs checked by a CI test -- score normalized to 8 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 0/30 approved changesets -- score normalized to 0 |
| Contributors | met | 2.5 / 2.5 | project has 28 contributing companies or organizations |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | excluded | 0 / 5 | no dependencies found |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | met | 5 / 5 | security policy file detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | met | 7.5 / 7.5 | 0 existing vulnerabilities detected |

### Dependency advisories — 100/100 (Excellent)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 4 resolved dependencies against OSV; 8 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

### High-Risk Jurisdiction Exposure — 50/100 (Moderate)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | partial | 50 / 100 | Russia: top_contributor (1) |

## AI Readiness — 70/100 (Good)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

### Agent context & guidance — 75/100 (Good)

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | AGENTS.md, CLAUDE.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 71/100 (Good)

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | met | 18 / 18 | Makefile |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .php-cs-fixer.dist.php |
| Static type checking | not met | 0 / 11 | — |
| Reproducible environment | not met | 0 / 10 | — |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

### Code legibility for models — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | not met | 0 / 45 | PHP without a type-check config |
| Manageable file sizes | met | 55 / 55 | 0/4 source files over 60KB |

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt