# phcdevworks/spectre-tokens — health index 66/100 (Moderate)

> Inspection of the public repository phcdevworks/spectre-tokens by inspect.software. It holds a health index of 66 out of 100, placing it in the Moderate 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/phcdevworks/spectre-tokens
- Report page: https://inspect.software/software/phcdevworks/spectre-tokens
- Full JSON report: https://inspect.software/api/repositories/phcdevworks/spectre-tokens/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/p/phcdevworks/spectre-tokens.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% | 90/100 | Excellent |
| Community & Adoption | 18% | 47/100 | At risk |
| Sustainability & Governance | 24% | 56/100 | Moderate |
| Engineering Quality | 20% | 67/100 | Moderate |
| Security | 16% | 65/100 | Moderate |
| AI Readiness | not counted | 68/100 | Moderate |

## Repository facts

| Field | Value |
|---|---|
| Description | @phcdevworks/spectre-tokens is the design-token package of the Spectre system. It provides a complete, UI-ready token surface for downstream Spectre packages and compatible applications. |
| Homepage | https://go.phcdev.co/ |
| Primary language | TypeScript |
| License | MIT |
| Stars | 2 |
| Forks | 0 |
| Created | 2025-11-21 |
| Last push | 2026-07-17 |
| Latest release | v3.4.0 |
| Commits (last year) | 489 |
| Bus factor | 1 |
| Topics | design-systems, npm, npm-package, npm-package-typescript, spectre-design-system, ui-design, design-tokens, design-tools |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | @phcdevworks/spectre-tokens | 3.4.0 | 2,485 |

## Vitality — 90/100 (Excellent)

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

### Development activity — 83/100 (Good)

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

### Release discipline — 100/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 | 27 releases published |
| Release recency | met | 36 / 36 | latest release 4 days ago |
| Release cadence | met | 27 / 27 | a release every ~6.3 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 — 47/100 (At risk)

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

### Popularity & adoption — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | not met | 0 / 60 | 2 stars |
| Forks | not met | 0 / 25 | 0 forks |
| Watchers | not met | 0 / 15 | 1 watchers |

### Community health — 92/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 | not met | 0 / 7.2 | — |
| PR template | met | 6.3 / 6.3 | — |

### Ecosystem adoption (downloads) — 57/100 (Moderate)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 45.3 / 80 | 2,485 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 56/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) — 22/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 4.5 / 22.5 | top contributor authored 80% of commits |
| Contributor breadth | partial | 5.4 / 13.5 | 4 contributors |
| OpenSSF Scorecard: Contributors | partial | 3 / 10 | project has 1 contributing companies or organizations -- score normalized to 3 |

### Issue & PR responsiveness — 65/100 (Moderate)

Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 46.8 | no issues or no data |
| PR acceptance | partial | 34.6 / 38.2 | 85/94 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 3.4 / 25 | 2 followers of phcdevworks |
| Track record | partial | 21.1 / 25 | 17 public repos, account ~7 yr old |

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

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

## Engineering Quality — 67/100 (Moderate)

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

### Engineering practices — 68/100 (Moderate)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 1 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | not met | 0 / 16 | — |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | no pull request found |

### Documentation — 65/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://go.phcdev.co/ |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 8 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 65/100 (Moderate)

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 — 56/100 (Moderate)

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 2.2 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | excluded | 0 / 2.5 | no pull request found |
| 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 | partial | 0.8 / 2.5 | project has 1 contributing companies or organizations -- score normalized to 3 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | met | 7.5 / 7.5 | 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 0 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 | no SAST tool detected |
| Security-Policy | partial | 2 / 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 369 resolved dependencies against OSV. 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 — 100/100 (Excellent)

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 | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 68/100 (Moderate)

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 | .github/copilot-instructions.md, 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) — 60/100 (Moderate)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | partial | 5 / 8 | dependency automation configured, none observed in the sampled commits |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

### Code legibility for models — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | met | 55 / 55 | 0/42 source files over 60KB |

### Machine-readable interfaces — 40/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | not met | 0 / 40 | — |
| MCP server | not met | 0 / 20 | — |
| Runnable examples | met | 40 / 40 | example |

## Collection warnings

- deps.dev does not index npm:@phcdevworks/spectre-tokens@3.4.0; advisories assessed against the repository dependency graph instead

## 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