Public record
Software health reportschema 0.23.0 · metrics 2.10.0 · 2026-07-21 21:20 UTC

51Degrees / pipeline-node

51Degrees Pipeline for Node.js

JavaScriptCustom license★ 0 stars⑂ 2 forkssince Oct 2019View on GitHub ↗

51Degrees/pipeline-node holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (81/100) and lowest on Community & Adoption (40/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

75
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.

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

Ownership

51DegreesOrganization
24 followers90 public repossince Jun 2013

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?

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
13.8/36Commit cadence20/52 weeks with commits
15.2/18Commit volume48 commits in the last year
10/10OpenSSF Scorecard: Maintained28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year48
human_commit_share1
days_since_last_push1
active_weeks_last_year20
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~4.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag4.5.29
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases4.1

Community & Adoption

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

40Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks2 forks
1.7/15Watchers3 watchers
Inputs used
forks2
stars0
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
76.8/80Monthly downloads577,105 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesfiftyone.pipeline.did, fiftyone.pipeline.core, fiftyone.pipeline.engines, fiftyone.pipeline.translation, fiftyone.pipeline.engines.fiftyone, fiftyone.pipeline.cloudrequestengine
dependents
ecosystemsnpm
total_downloads
monthly_downloads577,105
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?

79Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.1/22.5Commit distributiontop contributor authored 46% of commits
13.5/13.5Contributor breadth15 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled15
top_contributor_share0.464
How it's scored
37/42Issue resolution88% of issues closed
28.1/30PR acceptance147/157 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 12/21 approved changesets -- score normalized to 5
Inputs used
merged_prs147
open_issues2
closed_issues15
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.882
closed_unmerged_prs10
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
10.1/25Owner reach24 followers of 51Degrees
25/25Track record90 public repos, account ~13 yr old
Inputs used
followers24
owner_typeOrganization
is_verified
owner_login51Degrees
public_repos90
account_age_days4,786
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable6 package(s) on npm
35/35Publish recencylatest publish 4 days ago
20/20Version history158 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesfiftyone.pipeline.did, fiftyone.pipeline.core, fiftyone.pipeline.engines, fiftyone.pipeline.translation, fiftyone.pipeline.engines.fiftyone, fiftyone.pipeline.cloudrequestengine
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests13 out of 21 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.5/2.5CI-Tests13 out of 21 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 12/21 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
33.6/40Legible commit history63 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.63
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc
11/11Static type checkingfiftyone.pipeline.cloudrequestengine/tsconfig.json, fiftyone.pipeline.core/tsconfig.json, fiftyone.pipeline.engines.fiftyone/tsconfig.json, fiftyone.pipeline.engines/tsconfig.json, tsconfig.json
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsfiftyone.pipeline.cloudrequestengine/tsconfig.json, fiftyone.pipeline.core/tsconfig.json, fiftyone.pipeline.engines.fiftyone/tsconfig.json, fiftyone.pipeline.engines/tsconfig.json, tsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeJavaScript with type-check config (fiftyone.pipeline.cloudrequestengine/tsconfig.json, fiftyone.pipeline.core/tsconfig.json, fiftyone.pipeline.engines.fiftyone/tsconfig.json, fiftyone.pipeline.engines/tsconfig.json, tsconfig.json)
55/55Manageable file sizes0/133 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes16,572
source_files_sampled133
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

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

Data collection warnings

  • deps.dev does not index npm:fiftyone.pipeline.did@4.5.29; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks

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.

111222212020-112022-022023-05

Each point covers 3 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-07-21 21:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests13 out of 21 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 12/21 approved changesets -- score normalized to 5
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
npmfiftyone.pipeline.corefile:../fiftyone.pipeline.corefiftyone.pipeline.cloudrequestengine/package.json
npmfiftyone.pipeline.enginesfile:../fiftyone.pipeline.enginesfiftyone.pipeline.cloudrequestengine/package.json
npmmustache^4.2.0fiftyone.pipeline.core/package.json
npmuglify-js^3.19.3fiftyone.pipeline.core/package.json
npmowidgithub:51Degrees/owid-js#mainfiftyone.pipeline.did/package.json
npmfiftyone.pipeline.corefile:../fiftyone.pipeline.corefiftyone.pipeline.engines.fiftyone/package.json
npmfiftyone.pipeline.enginesfile:../fiftyone.pipeline.enginesfiftyone.pipeline.engines.fiftyone/package.json
npmfiftyone.pipeline.corefile:../fiftyone.pipeline.corefiftyone.pipeline.engines/package.json
npmfiftyone.pipeline.corefile:../fiftyone.pipeline.corefiftyone.pipeline.translation/package.json
npmjs-yaml^4.3.0fiftyone.pipeline.translation/package.json
All dependencies 12

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

RegistryPackageVersionRelation
npmjs-yaml^4.3.0direct
npmmustache^4.2.0direct
npmuglify-js^3.19.3direct
npm@types/jest^27.5.2indirect
npm@types/node^20.14.10indirect
npm@types/node^20.19.43indirect
npmjest^27.5.1indirect
npmjest^29.7.0indirect
npmjest-each^27.5.1indirect
npmnode-mocks-http^1.18.1indirect
npmtypescript^5.5.3indirect
npmtypescript^5.9.3indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.23.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.