# flyfish-dev/styled-exceljs — health index 75/100 (Good)

> Inspection of the public repository flyfish-dev/styled-exceljs by inspect.software. It holds a health index of 75 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/flyfish-dev/styled-exceljs
- Report page: https://inspect.software/software/flyfish-dev/styled-exceljs
- Full JSON report: https://inspect.software/api/repositories/flyfish-dev/styled-exceljs/report
- Badge: https://inspect.software/badge/v1/flyfish-dev/styled-exceljs.svg
- Inspected: 2026-10-19
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 71/100 | Good |
| Community & Adoption | 17% | 47/100 | Weak |
| Sustainability & Governance | 23% | 54/100 | Moderate |
| Engineering Quality | 19% | 86/100 | Excellent |
| Security | 16% | 66/100 | Good |
| AI Readiness | 4% | 64/100 | Moderate |

The weighted overall 65 is calibrated to 75 on the published index scale (record calibration 2026-08-02).

## Repository facts

| Field | Value |
|---|---|
| Description | Styled SheetJS-compatible Excel parser and renderer |
| Classification | library, cli |
| Homepage | https://www.npmjs.com/package/styled-exceljs |
| Primary language | JavaScript |
| License | Apache-2.0 |
| Stars | 3 |
| Forks | 2 |
| Created | 2026-04-27 |
| Last push | 2026-10-11 |
| Latest release | v0.21.6 |
| Commits (last year) | 29 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | styled-exceljs | 0.21.6 | 71,237 |

## Vitality — 71/100 (Good)

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

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 2 releases published |
| Release recency | met | 36 / 36 | latest release 40 days ago |
| Release cadence | met | 27 / 27 | a release every ~0.4 days |
| OpenSSF Scorecard: Signed-Releases | not met | 0 / 10 | Project has not signed or included provenance with any releases. |

### Abandonment — 100/100 (Exceptional)

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

## Community & Adoption — 47/100 (Weak)

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

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (Apache-2.0) |
| 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) — 81/100 (Excellent)

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

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

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

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

### Maintainer resilience (bus factor) — 39/100 (Weak)

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

### Issue & PR responsiveness — 35/100 (Weak)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 42 | no issues or no data |
| PR acceptance | partial | 7.5 / 30 | 1/4 decided PRs merged |
| Newcomer PR acceptance | met | 13 / 13 | 1/1 first-time contributors' PRs merged in 30d |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 11.8 / 25 | 43 followers of flyfish-dev |
| Track record | partial | 12.8 / 25 | 43 public repos, account ~0 yr old |

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

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

## Engineering Quality — 86/100 (Excellent)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 5 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .eslintrc, eslint.config.mjs |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | met | 20 / 20 | 1 out of 1 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://www.npmjs.com/package/styled-exceljs |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | met | 10 / 10 | — |

## Security — 66/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 — 58/100 (Moderate)

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

| 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 | met | 2.5 / 2.5 | 1 out of 1 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 | not met | 0 / 7.5 | Found 0/30 approved changesets -- score normalized to 0 |
| Contributors | met | 2.5 / 2.5 | project has 13 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 | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 22 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 | met | 5 / 5 | all dependencies are pinned |
| SAST | met | 5 / 5 | SAST tool is run on all commits |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | not met | 0 / 7.5 | Project has not signed or included provenance with any releases. |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | met | 7.5 / 7.5 | 0 existing vulnerabilities detected |

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

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 645 resolved dependencies against OSV; 12 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 (Exceptional)

| 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 (Exceptional)

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

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 27/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 | partial | 26.7 / 40 | 50 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 87/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | met | 18 / 18 | Makefile, modules/Makefile, packages/dta/Makefile, packages/otorp/Makefile, packages/s/Makefile, packages/ssf/Makefile, types/Makefile |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc, eslint.config.mjs |
| Static type checking | met | 11 / 11 | packages/s/tsconfig.json, packages/ssf/types/tsconfig.json, types/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 | partial | 5 / 8 | dependency automation configured, none observed in the sampled commits |
| OpenSSF Scorecard: Pinned-Dependencies | met | 10 / 10 | all dependencies are pinned |

### Code legibility for models — 78/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | partial | 27 / 45 | JavaScript with type-check config (packages/s/tsconfig.json, packages/ssf/types/tsconfig.json, types/tsconfig.json) |
| Manageable file sizes | partial | 50.6 / 55 | 20/252 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