# eemeli/yaml — health index 78/100 (Good)

> Inspection of the public repository eemeli/yaml by inspect.software. It holds a health index of 78 out of 100, placing it in the Good 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/eemeli/yaml
- Report page: https://inspect.software/software/eemeli/yaml
- Full JSON report: https://inspect.software/api/repositories/eemeli/yaml/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/e/eemeli/yaml.svg
- Inspected: 2026-07-22
- Methodology: metrics 1.13.0, report schema 0.27.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 79/100 | Good |
| Community & Adoption | 18% | 80/100 | Good |
| Sustainability & Governance | 24% | 66/100 | Moderate |
| Engineering Quality | 20% | 90/100 | Excellent |
| Security | 16% | 79/100 | Good |
| AI Readiness | not counted | 58/100 | Moderate |

## Repository facts

| Field | Value |
|---|---|
| Description | YAML parser and serialiser for JavaScript |
| Homepage | https://eemeli.org/yaml |
| Primary language | TypeScript |
| License | ISC |
| Stars | 1,681 |
| Forks | 172 |
| Created | 2018-01-29 |
| Last push | 2026-07-13 |
| Latest release | v2.9.0 |
| Commits (last year) | 94 |
| Bus factor | 1 |
| Topics | yaml, yaml-parser, yaml-editor |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | yaml | 2.9.0 | 741,511,044 |

## Vitality — 79/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | partial | 28.8 / 36 | last push 9 days ago |
| Commit cadence | partial | 14.5 / 36 | 21/52 weeks with commits |
| Commit volume | partial | 17.8 / 18 | 94 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 8 commit(s) and 7 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 | 89 releases published |
| Release recency | met | 36 / 36 | latest release 72 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~55.1 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 | last human commit 9 days ago |

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

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

### Popularity & adoption — 77/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 52.3 / 60 | 1,681 stars |
| Forks | partial | 18.6 / 25 | 172 forks |
| Watchers | partial | 6.4 / 15 | 15 watchers |

### Community health — 70/100 (Good)

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | met | 80 / 80 | 741,511,044 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 66/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) — 33/100 (At risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 43.7 / 46.8 | 94% of issues closed |
| PR acceptance | partial | 30.1 / 38.2 | 140/178 decided PRs merged |
| OpenSSF Scorecard: Code-Review | partial | 1.5 / 15 | Found 2/13 approved changesets -- score normalized to 1 |

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

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | partial | 10 / 30 | personal (user) account |
| Verified domain | excluded | 0 / 20 | not applicable to user accounts |
| Owner reach | partial | 19.2 / 25 | 467 followers of eemeli |
| Track record | met | 25 / 25 | 144 public repos, account ~15 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 72 days ago |
| Version history | met | 20 / 20 | 103 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 90/100 (Excellent)

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

### Engineering practices — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 6 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | eslint.config.js |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | met | 20 / 20 | 4 out of 4 merged PRs checked by a CI test -- score normalized to 10 |

### Documentation — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://eemeli.org/yaml |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 3 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 79/100 (Good)

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 — 74/100 (Good)

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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 | met | 2.5 / 2.5 | 4 out of 4 merged PRs checked by a CI test -- score normalized to 10 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | partial | 0.8 / 7.5 | Found 2/13 approved changesets -- score normalized to 1 |
| Contributors | met | 2.5 / 2.5 | project has 19 contributing companies or organizations |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | met | 5 / 5 | project is fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 8 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | partial | 1 / 5 | dependency not pinned by hash detected -- score normalized to 2 |
| SAST | met | 5 / 5 | SAST tool is run on all commits |
| Security-Policy | met | 5 / 5 | security policy file detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | partial | 6.8 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | partial | 3 / 7.5 | 6 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 219 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 — 58/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 — 40/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | met | 40 / 40 | 78 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 56/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | eslint.config.js |
| Static type checking | met | 11 / 11 | tests/tsconfig.json, tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 2 / 10 | dependency not pinned by hash detected -- score normalized to 2 |

### 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/111 source files over 60KB |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

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