Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 07:55 UTC

semantic-release / env-ci

Get environment variables exposed by CI services

JavaScriptMIT★ 241 stars⑂ 47 forkssince Dec 2017View on GitHub ↗

semantic-release/env-ci holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (75/100) and lowest on AI Readiness (42/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

Semantic ReleaseOrganization
406 followers37 public repossince Jun 2015

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

Package ecosystems

Metrics by category

Vitality

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

54Moderate · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
2.4/36Commit cadence — 46/52 weeks with commits, discounted for automation: 3 of the last 100 commits human-authored, spanning 377 days
1.3/18Commit volume — 81 commits in the last year, discounted for automation: 3 of the last 100 commits human-authored, spanning 377 days
10/10OpenSSF Scorecard: Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year81
human_commit_share0.03
days_since_last_push1
active_weeks_last_year46
How it's scored
27/27Ships releases — 78 releases published
7.2/36Release recency — latest release 378 days ago
19.8/27Release cadence — a release every ~103.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count78
latest_release_tagv11.2.0
releases_from_tagsno
days_since_latest_release378
mean_days_between_releases103.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?

73Good · 17% of overall
How it's scored
38.6/60Stars — 241 stars
13.9/25Forks — 47 forks
3.3/15Watchers — 5 watchers
Inputs used
forks47
stars241
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 13,924,315 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesenv-ci
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads13,924,315
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.4/22.5Commit distribution — top contributor authored 40% of commits
13.5/13.5Contributor breadth — 26 contributors
10/10OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled26
top_contributor_share0.405
How it's scored
37.3/42Issue resolution — 89% of issues closed
28.3/30PR acceptance — 475/504 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs475
open_issues4
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.889
closed_unmerged_prs29
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, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
18.8/25Owner reach — 406 followers of semantic-release
23.5/25Track record — 37 public repos, account ~11 yr old
Inputs used
followers406
owner_typeOrganization
is_verifiedno
owner_loginsemantic-release
public_repos37
account_age_days4,112
How it's scored
25/25Published & resolvable — 1 package(s) on npm
14/35Publish recency — latest publish 378 days ago
20/20Version history — 81 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesenv-ci
ecosystemsnpm
any_deprecatedno
min_days_since_publish378

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/env-ci
10/10Repository description
10/10Topics — 20 topics
0/10Wiki
Inputs used
topicsappveyor, buildkite, ci, circleci, codeship, drone, environment, gitlab, jenkins, semaphore, shippable, wercker, travis, continuous-integration, bamboo, bitrise, bitbucket, vsts, cirrus-ci, buddy
has_wikino
homepagehttps://www.npmjs.com/package/env-ci
docs_sitehttps://www.npmjs.com/package/env-ci
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

71Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 30 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 — no data
2.5/2.5Contributors — project has 20 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 23 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Branch-Protection, Code-Review, 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_packages18
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:env-ci@11.2.0 runtime dependency closure — what installing the published package pulls in — 18 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://buildkite.com/llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://buildkite.com/llms.txt
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
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 97 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.97
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/71 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,763
source_files_sampled71
oversized_source_files0

Key facts

241GitHub stars
26contributors
81commits, last 12 months
1days since last push
78releases
2bus factor
4open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 47 ⇿
0Stars
47Forks
76Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

010203040504622017-122021-122025-12
Major 10Minor 31Patch 32

Each point covers 8 days.

OpenSSF Scorecard 6.4 / 10
6.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 07:54 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 30 changesets
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmexeca^8.0.0package.json
npmjava-properties^1.0.2package.json
All dependencies 187

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

RegistryPackageVersionRelation
npmexeca8.0.1direct
npmjava-properties1.0.2direct
npm@bcoe/v8-coverage1.0.2indirect
npm@cto.af/wtf80.0.5indirect
npm@isaacs/fs-minipass4.0.1indirect
npm@istanbuljs/schema0.1.6indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.6.0indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@mapbox/node-pre-gyp2.0.3indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@rollup/pluginutils5.4.0indirect
npm@sindresorhus/merge-streams4.0.0indirect
npm@types/estree1.0.9indirect
npm@types/istanbul-lib-coverage2.0.6indirect
npm@vercel/nft1.11.0indirect
npmabbrev3.0.1indirect
npmacorn8.18.0indirect
npmacorn-import-attributes1.9.5indirect
npmacorn-walk8.3.5indirect
npmagent-base7.1.4indirect
npmansi-regex6.3.0indirect
npmansi-styles6.2.3indirect
npmargparse1.0.10indirect
npmarray-find-index1.0.2indirect
npmarrgv1.0.2indirect
npmarrify3.0.0indirect
npmasync-sema3.1.1indirect
npmava8.0.1indirect
npmbalanced-match4.0.4indirect
npmbindings1.5.0indirect
npmblueimp-md52.19.0indirect
npmbrace-expansion5.0.9indirect
npmbraces3.0.3indirect
npmc812.0.0indirect
npmcallsites4.2.0indirect
npmcbor22.3.0indirect
npmchalk5.6.2indirect
npmchownr3.0.0indirect
npmchunkd2.0.1indirect
npmci-info4.4.0indirect
npmci-parallel-vars1.0.1indirect
npmcli-truncate6.1.1indirect
npmcliui9.0.1indirect
npmcode-excerpt4.0.0indirect
npmcommon-path-prefix3.0.0indirect
npmconcordance5.0.4indirect
npmconsola3.4.2indirect
npmconvert-source-map2.0.0indirect
npmconvert-to-spaces2.0.1indirect
npmcross-spawn7.0.6indirect
npmcrypto-random-string4.0.0indirect
npmcurrently-unhandled0.4.1indirect
npmdate-time3.1.0indirect
npmdebug4.4.3indirect
npmdetect-libc2.1.2indirect
npmemittery2.0.0indirect
npmemoji-regex10.6.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp2.0.0indirect
npmescape-string-regexp5.0.0indirect
npmesprima4.0.1indirect
npmestree-walker2.0.2indirect
npmesutils2.0.3indirect
npmfast-diff1.3.0indirect
npmfast-glob3.3.3indirect
npmfastq1.20.3indirect
npmfigures6.1.0indirect
npmfile-uri-to-path1.0.0indirect
npmfile-url4.0.0indirect
npmfill-range7.1.1indirect
npmfind-up5.0.0indirect
npmfind-up-simple1.0.1indirect
npmforeground-child3.3.1indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmget-stream8.0.1indirect
npmglob13.0.6indirect
npmglob-parent5.1.2indirect
npmglobby16.2.4indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhtml-escaper2.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmhuman-signals5.0.0indirect
npmignore7.0.9indirect
npmignore-by-default2.1.0indirect
npmindent-string5.0.0indirect
npmirregular-plurals4.2.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point5.1.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-path-inside4.0.0indirect
npmis-plain-object5.1.0indirect
npmis-promise4.0.0indirect
npmis-stream3.0.0indirect
npmis-unicode-supported2.1.0indirect
npmisexe2.0.0indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmjs-string-escape1.0.1indirect
npmjs-yaml3.15.2indirect
npmload-json-file7.0.1indirect
npmlocate-path6.0.0indirect
npmlodash4.18.1indirect
npmlru-cache11.5.2indirect
npmmake-dir4.0.0indirect
npmmatcher6.0.0indirect
npmmd5-hex3.0.1indirect
npmmemoize11.0.0indirect
npmmerge-stream2.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmmimic-fn4.0.0indirect
npmmimic-function5.0.1indirect
npmminimatch10.2.6indirect
npmminipass7.1.3indirect
npmminizlib3.1.0indirect
npmms2.1.3indirect
npmnode-fetch2.7.0indirect
npmnode-gyp-build4.8.4indirect
npmnopt8.1.0indirect
npmnpm-run-path5.3.0indirect
npmonetime6.0.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmp-map7.0.8indirect
npmpackage-config5.0.0indirect
npmparse-ms4.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-key4.0.0indirect
npmpath-scurry2.0.2indirect
npmpicomatch2.3.2indirect
npmpicomatch4.0.7indirect
npmplur6.0.0indirect
npmprettier3.9.6indirect
npmpretty-ms9.3.1indirect
npmqueue-microtask1.2.3indirect
npmresolve-cwd3.0.0indirect
npmresolve-from5.0.0indirect
npmreusify1.1.0indirect
npmrun-parallel1.2.0indirect
npmsemver7.8.5indirect
npmserialize-error7.0.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmslash5.1.0indirect
npmslice-ansi9.0.0indirect
npmsprintf-js1.0.3indirect
npmstack-utils2.0.6indirect
npmstring-width7.2.0indirect
npmstring-width8.2.2indirect
npmstrip-ansi7.2.0indirect
npmstrip-final-newline3.0.0indirect
npmsupertap3.0.1indirect
npmsupports-color7.2.0indirect
npmtar7.5.22indirect
npmtemp-dir3.0.0indirect
npmtempy3.2.0indirect
npmtest-exclude8.0.0indirect
npmtime-zone1.0.0indirect
npmto-regex-range5.0.1indirect
npmtr460.0.3indirect
npmtype-fest0.13.1indirect
npmtype-fest1.4.0indirect
npmtype-fest2.19.0indirect
npmunicorn-magic0.4.0indirect
npmunique-string3.0.0indirect
npmv8-to-istanbul9.3.0indirect
npmwebidl-conversions3.0.1indirect
npmwell-known-symbols2.0.0indirect
npmwhatwg-url5.0.0indirect
npmwhich2.0.2indirect
npmwrap-ansi9.0.2indirect
npmwrite-file-atomic7.0.1indirect
npmy18n5.0.8indirect
npmyallist5.0.0indirect
npmyargs18.1.0indirect
npmyargs-parser21.1.1indirect
npmyargs-parser22.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:env-ci@11.2.0 pulls in 18 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.