Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 16:32 UTC

bifravst / prettier-config

Prettier config for our projects

JavaScriptBSD-3-Clause★ 0 stars⑂ 0 forkssince Feb 2024View on GitHub ↗

bifravst/prettier-config holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (80/100) and lowest on AI Readiness (28/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

63
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

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

Ownership

BifravstOrganization
8 followers49 public repossince Jun 2019

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@bifravst/prettier-config2.0.05,5182432 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

80Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
13.2/36Commit cadence — 19/52 weeks with commits
13.3/18Commit volume — 29 commits in the last year
10/10OpenSSF Scorecard: Maintained — 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year29
human_commit_share0.182
days_since_last_push4
active_weeks_last_year19
How it's scored
27/27Ships releases — 24 releases published
36/36Release recency — latest release 32 days ago
19.8/27Release cadence — a release every ~46.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count24
latest_release_tagv2.0.0
releases_from_tagsno
days_since_latest_release32
mean_days_between_releases46.7
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

46Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
49.9/80Monthly downloads — 5,518 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@bifravst/prettier-config
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,518
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 21 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
21/42Issue resolution — 50% of issues closed
20.8/30PR acceptance — 34/49 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs34
open_issues1
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs15
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.9/25Owner reach — 8 followers of bifravst
24.4/25Track record — 49 public repos, account ~7 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedno
owner_loginbifravst
public_repos49
account_age_days2,649

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 32 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@bifravst/prettier-config
ecosystemsnpm
any_deprecatedno
min_days_since_publish32

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — package.json ("prettier")
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 12 out of 13 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/bifravst/prettier-config
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://github.com/bifravst/prettier-config
docs_sitehttps://github.com/bifravst/prettier-config
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

64Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.2/2.5CI-Tests — 12 out of 13 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/28 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 21 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@bifravst/prettier-config@2.0.0 runtime dependency closure — what installing the published package pulls in — 2 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

28At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — package.json ("prettier")
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 99
8/8Automated maintenance — 81 of the last 99 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.818
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/1 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes67
source_files_sampled1
oversized_source_files0

Key facts

0GitHub stars
1contributors
29commits, last 12 months
4days since last push
24releases
1bus factor
1open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.5 / 10
5.5aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-18 16:32 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests12 out of 13 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/28 approved changesets -- score normalized to 0
10Contributorsproject has 21 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmprettier3.9.6package.json
npmprettier-plugin-organize-imports4.3.0package.json
All dependencies 94

Full resolved dependency set from the GitHub dependency graph: 2 direct and 92 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmprettier3.9.6direct
npmprettier-plugin-organize-imports4.3.0direct
npm@babel/code-frame7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@commitlint/cli21.2.2indirect
npm@commitlint/config-conventional21.2.2indirect
npm@commitlint/config-validator21.2.0indirect
npm@commitlint/ensure21.2.0indirect
npm@commitlint/execute-rule21.0.1indirect
npm@commitlint/format21.2.2indirect
npm@commitlint/is-ignored21.2.2indirect
npm@commitlint/lint21.2.2indirect
npm@commitlint/load21.2.2indirect
npm@commitlint/message21.2.0indirect
npm@commitlint/parse21.2.2indirect
npm@commitlint/read21.2.1indirect
npm@commitlint/resolve-extends21.2.2indirect
npm@commitlint/rules21.2.2indirect
npm@commitlint/to-lines21.0.1indirect
npm@commitlint/top-level21.2.0indirect
npm@commitlint/types21.2.0indirect
npm@conventional-changelog/git-client3.1.2indirect
npm@conventional-changelog/template1.3.0indirect
npm@simple-libs/child-process-utils2.0.0indirect
npm@simple-libs/stream-utils2.0.0indirect
npm@types/node26.2.0indirect
npmajv8.20.0indirect
npmansi-regex6.3.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmargue-cli3.1.0indirect
npmcallsites3.1.0indirect
npmchalk3.0.0indirect
npmcheck-node-version4.2.1indirect
npmcliui9.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommitlint21.2.2indirect
npmconventional-changelog-angular9.3.0indirect
npmconventional-changelog-conventionalcommits10.3.0indirect
npmconventional-commits-parser7.1.2indirect
npmcosmiconfig9.0.2indirect
npmcosmiconfig-typescript-loader6.3.0indirect
npmemoji-regex10.6.0indirect
npmenv-paths2.2.1indirect
npmerror-ex1.3.4indirect
npmes-toolkit1.51.0indirect
npmescalade3.2.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.5indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmglobal-directory5.0.0indirect
npmhas-flag4.0.0indirect
npmhusky9.1.7indirect
npmimport-fresh3.3.1indirect
npmini6.0.0indirect
npmis-arrayish0.2.1indirect
npmis-plain-obj4.1.0indirect
npmjiti2.6.1indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.3.1indirect
npmjson-parse-even-better-errors2.3.1indirect
npmjson-schema-traverse1.0.0indirect
npmlines-and-columns1.2.4indirect
npmlint-staged17.5.1indirect
npmmap-values1.0.1indirect
npmminimist1.2.8indirect
npmobject-filter1.0.2indirect
npmparent-module1.0.1indirect
npmparse-json5.2.0indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.7indirect
npmqueue-microtask1.2.3indirect
npmrequire-from-string2.0.2indirect
npmresolve-from4.0.0indirect
npmresolve-from5.0.0indirect
npmrun-parallel1.2.0indirect
npmsemver6.3.1indirect
npmsemver7.8.5indirect
npmstring-argv0.3.2indirect
npmstring-width7.2.0indirect
npmstring-width8.2.2indirect
npmstrip-ansi7.2.0indirect
npmsupports-color7.2.0indirect
npmtinyexec1.3.1indirect
npmtypescript5.5.4indirect
npmundici-types8.3.0indirect
npmwrap-ansi9.0.2indirect
npmy18n5.0.8indirect
npmyaml2.9.0indirect
npmyargs18.1.0indirect
npmyargs-parser22.0.0indirect
Dependency advisories 0

Installing npm:@bifravst/prettier-config@2.0.0 pulls in 2 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.