Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 18:38 UTC

jpillora / node-glob-all

Provide multiple patterns to node-glob

JavaScriptNo license detected★ 56 stars⑂ 7 forkssince Mar 2013View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

jpillora/node-glob-all holds a health index of 35 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (57/100) and lowest on Vitality (20/100). It was last updated 205 days ago. A single contributor accounts for most of its recent work.

35
overall / 100
Weak

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.

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

Ownership

Jaime PilloraPersonal account
1,764 followers296 public repossince Feb 2011

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
npmglob-all3.3.11,871,456131447 days agoglobmultiallmanifestgenerationfile

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
3.6/36Push recency — last push 205 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.925
days_since_last_push205
active_weeks_last_year0
How it's scored
27/27Ships releases — 2 releases published
0/36Release recency — latest release 1,447 days ago
12.6/27Release cadence — a release every ~235.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv3.3.1
releases_from_tagsno
days_since_latest_release1,447
mean_days_between_releases235.2
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?

48Weak · 17% of overall
How it's scored
28.2/60Stars — 56 stars
6.5/25Forks — 7 forks
1.7/15Watchers — 3 watchers
Inputs used
forks7
stars56
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescircleci.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 1,871,456 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesglob-all
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,871,456
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.9/22.5Commit distribution — top contributor authored 78% of commits
10.8/13.5Contributor breadth — 8 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.783
How it's scored
32.1/42Issue resolution — 76% of issues closed
22.5/30PR acceptance — 12/16 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 5/14 approved changesets -- score normalized to 3
Inputs used
merged_prs12
open_issues4
closed_issues13
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.765
closed_unmerged_prs4
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
23.3/25Owner reach — 1,764 followers of jpillora
25/25Track record — 296 public repos, account ~15 yr old
Inputs used
followers1,764
owner_typeUser
is_verified—
owner_loginjpillora
public_repos296
account_age_days5,716
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,447 days ago
20/20Version history — 13 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesglob-all
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,447

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 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 9 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

Documentation

50Moderate
How it's scored
30/30README
0/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_dirno
has_descriptionyes

Security

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

45Weak · 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
0/2.5CI-Tests — 0 out of 9 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
2.2/7.5Code-Review — Found 5/14 approved changesets -- score normalized to 3
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not 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
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
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.1
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_packages37
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:glob-all@3.3.1 runtime dependency closure — what installing the published package pulls in — 37 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.6/40Legible commit history — 18 of 49 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.367
agent_instruction_files—
agent_instruction_max_bytes—
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 53
8/8Automated maintenance — 4 of the last 53 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_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.075
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/7 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes4,882
source_files_sampled7
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
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

56GitHub stars
8contributors
0commits, last 12 months
205days since last push
2releases
1bus 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 ★ / 7 ⇿
0Stars
7Forks

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.

1234567712014-062018-042022-03

Each point covers 8 days.

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-10-18 18:38 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 5/14 approved changesets -- score normalized to 3
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmglob^7.2.3package.json
npmyargs^15.3.1package.json
All dependencies 89

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

RegistryPackageVersionRelation
npmglob7.2.3direct
npmyargs15.3.1direct
npm@types/color-name1.1.1indirect
npmansi-regex5.0.1indirect
npmansi-styles4.2.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmcall-bind1.0.2indirect
npmcamelcase5.3.1indirect
npmcliui6.0.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmdecamelize1.2.0indirect
npmdeep-equal1.1.1indirect
npmdefine-properties1.1.4indirect
npmdefined1.0.0indirect
npmdotignore0.1.2indirect
npmemoji-regex8.0.0indirect
npmes-abstract1.20.4indirect
npmes-to-primitive1.2.1indirect
npmfind-up4.1.0indirect
npmfor-each0.3.3indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.1indirect
npmfunction.prototype.name1.1.5indirect
npmfunctions-have-names1.2.3indirect
npmget-caller-file2.0.5indirect
npmget-intrinsic1.1.3indirect
npmget-symbol-description1.0.0indirect
npmhas1.0.3indirect
npmhas-bigints1.0.2indirect
npmhas-property-descriptors1.0.0indirect
npmhas-symbols1.0.3indirect
npmhas-tostringtag1.0.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npminternal-slot1.0.3indirect
npmis-arguments1.1.1indirect
npmis-bigint1.0.4indirect
npmis-boolean-object1.1.2indirect
npmis-callable1.2.7indirect
npmis-core-module2.11.0indirect
npmis-date-object1.0.5indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-negative-zero2.0.2indirect
npmis-number-object1.0.7indirect
npmis-regex1.1.4indirect
npmis-shared-array-buffer1.0.2indirect
npmis-string1.0.7indirect
npmis-symbol1.0.4indirect
npmis-weakref1.0.2indirect
npmlocate-path5.0.0indirect
npmminimatch3.1.2indirect
npmminimist1.2.7indirect
npmobject-inspect1.12.2indirect
npmobject-is1.1.5indirect
npmobject-keys1.1.1indirect
npmobject.assign4.1.4indirect
npmonce1.4.0indirect
npmp-limit2.2.2indirect
npmp-locate4.1.0indirect
npmp-try2.2.0indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-parse1.0.7indirect
npmregexp.prototype.flags1.4.3indirect
npmrequire-directory2.1.1indirect
npmrequire-main-filename2.0.0indirect
npmresolve1.22.1indirect
npmresumer0.0.0indirect
npmsafe-regex-test1.0.0indirect
npmset-blocking2.0.0indirect
npmside-channel1.0.4indirect
npmstring-width4.2.0indirect
npmstring.prototype.trim1.2.6indirect
npmstring.prototype.trimend1.0.5indirect
npmstring.prototype.trimstart1.0.5indirect
npmstrip-ansi6.0.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtape4.16.1indirect
npmthrough2.3.8indirect
npmunbox-primitive1.0.2indirect
npmwhich-boxed-primitive1.0.2indirect
npmwhich-module2.0.0indirect
npmwrap-ansi6.2.0indirect
npmwrappy1.0.2indirect
npmy18n4.0.1indirect
npmyargs-parser18.1.3indirect
Dependency advisories 0

Installing npm:glob-all@3.3.1 pulls in 37 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.