Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 11:04 UTC

sam-barfield / Nginx

An NPM package used for installing and configuring NGINX virtual hosts.

JavaScriptCustom license★ 2 stars⑂ 0 forkssince Mar 2021View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

sam-barfield/Nginx holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Security (47/100) and lowest on Community & Adoption (28/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

29
overall / 100
At Risk

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.

29
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 39 is calibrated to 34 on the published index scale (record calibration 2026-08-02).

Ownership

Sam BarfieldPersonal account
2 followers12 public repossince Jul 2023

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmnginxpoints to another repo — not scored1.1.0179,16011521 days agonodenginxvirtualhosthelper

Metrics by category

Vitality

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

42Weak · 21% of overall

Development activity

36Weak
How it's scored
36/36Push recency — last push 7 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.984
days_since_last_push7
active_weeks_last_year0

Release discipline

52Moderate
How it's scored
27/27Ships releases — 2 releases published
0/36Release recency — latest release 1,524 days ago
19.8/27Release cadence — a release every ~103.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tag1.0.8
releases_from_tagsno
days_since_latest_release1,524
mean_days_between_releases103.9
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?

28At Risk · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

59Moderate
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

35Weak · 23% of overall

Maintainer resilience (bus factor)

13Critical
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
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

61Moderate
How it's scored
42/42Issue resolution — 100% of issues closed
10.8/30PR acceptance — 13/36 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs13
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs23
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.

Ownership & stewardship

35Weak
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
3.4/25Owner reach — 2 followers of sam-barfield
14.5/25Track record — 12 public repos, account ~3 yr old
Inputs used
followers2
owner_typeUser
is_verified—
owner_loginsam-barfield
public_repos12
account_age_days1,161
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall

Engineering practices

40Weak
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
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://npmjs.org/nginx
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://npmjs.org/nginx
docs_sitehttps://npmjs.org/nginx
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 16% of overall

Security posture

34At Risk
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
0/2.5CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/8 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Packaging, 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_packages21
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:nginx@1.1.0 runtime dependency closure — what installing the published package pulls in — 21 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.

29At Risk · 4% of overall

Agent context & guidance

12Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
12.2/40Legible commit history — 14 of 61 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.23
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

32At Risk
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — eslint.config.mjs
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 62
8/8Automated maintenance — 1 of the last 62 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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.016

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/3 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes9,735
source_files_sampled3
oversized_source_files0

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'nginx' points at a different repository (https://github.com/bwhybrow23/Nginx); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-15 11:04 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/8 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities20 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmchalk^4.1.2package.json
npmcommander^7.2.0package.json
npmprompt^1.3.0package.json
All dependencies 103

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

RegistryPackageVersionRelation
npmchalk4.1.2direct
npmcommander7.2.0direct
npmprompt1.3.0direct
npm@colors/colors1.5.0indirect
npm@eslint-community/eslint-utils4.5.1indirect
npm@eslint-community/regexpp4.12.1indirect
npm@eslint/config-array0.20.0indirect
npm@eslint/config-helpers0.2.1indirect
npm@eslint/core0.12.0indirect
npm@eslint/core0.13.0indirect
npm@eslint/eslintrc3.3.1indirect
npm@eslint/js9.24.0indirect
npm@eslint/object-schema2.1.6indirect
npm@eslint/plugin-kit0.2.8indirect
npm@humanfs/core0.19.1indirect
npm@humanfs/node0.16.6indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.3.1indirect
npm@humanwhocodes/retry0.4.2indirect
npm@types/estree1.0.7indirect
npm@types/json-schema7.0.15indirect
npmacorn8.14.1indirect
npmacorn-jsx5.3.2indirect
npmajv6.12.6indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmasync2.6.4indirect
npmasync3.2.3indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmcallsites3.1.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcolors1.0.3indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmcycle1.0.3indirect
npmdebug4.4.0indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint9.24.0indirect
npmeslint-scope8.3.0indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys4.2.0indirect
npmespree10.3.0indirect
npmesquery1.6.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmeyes0.1.8indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.3.3indirect
npmglob-parent6.0.2indirect
npmglobals14.0.0indirect
npmglobals16.0.0indirect
npmhas-flag4.0.0indirect
npmignore5.3.2indirect
npmimport-fresh3.3.1indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmisstream0.1.2indirect
npmjs-yaml4.1.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash4.17.21indirect
npmlodash.merge4.6.2indirect
npmminimatch3.1.2indirect
npmms2.1.3indirect
npmmute-stream0.0.8indirect
npmnatural-compare1.4.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmpunycode2.3.1indirect
npmread1.0.7indirect
npmresolve-from4.0.0indirect
npmrevalidator0.1.8indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstack-trace0.0.10indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtype-check0.4.0indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmwinston2.4.7indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:nginx@1.1.0 pulls in 21 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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with sam-barfield/Nginx. Read them side by side →

100metabase/metabaseThe easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:Exceptional100streamlit/streamlitStreamlit — A faster way to build and share data apps.Exceptional100mattermost/mattermostMattermost is an open source platform for secure collaboration across the entire software development lifecycle..Exceptional100scalar/scalarScalar is an open-source API platform:　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　🌐 Modern REST API Client　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　📖 Beautiful API References　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　✨ 1st-Class OpenAPI/Swagger SupportExceptional100nuxt/nuxtThe full-stack Vue framework.Exceptional100nodejs/undiciAn HTTP/1.1 client, written from scratch for Node.jsExceptional

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.