Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-30 16:51 UTC

gruntjs / grunt

Grunt: The JavaScript Task Runner

JavaScriptMIT★ 12,239 stars⑂ 1,489 forkssince Sep 2011View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

gruntjs/grunt holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Community & Adoption (95/100) and lowest on AI Readiness (33/100). It was last updated 16 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

gruntOrganization
187 followers68 public repossince Apr 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmgrunt1.6.34,558,4147333 days agotaskasynccliminifyuglifybuildlodashunittestqunitnodeunitserverinitscaffoldmakejaketool

Metrics by category

Vitality

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

51Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 16 days ago
6.9/36Commit cadence10/52 weeks with commits
10.3/18Commit volume13 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year13
human_commit_share1
days_since_last_push16
active_weeks_last_year10
How it's scored
27/27Ships releases12 releases published
0/36Release recencylatest release 1,307 days ago
19.8/27Release cadencea release every ~104.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count12
latest_release_tagv1.6.1
releases_from_tagsno
days_since_latest_release1,307
mean_days_between_releases104.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?

95Exceptional · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars12,239 stars
25/25Forks1,489 forks
14.8/15Watchers460 watchers
Inputs used
forks1,489
stars12,239
watchers460
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads4,558,414 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgrunt
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,558,414
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.5/22.5Commit distributiontop contributor authored 75% of commits
13.5/13.5Contributor breadth78 contributors
10/10OpenSSF Scorecard: Contributorsproject has 60 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled78
top_contributor_share0.754
How it's scored
37.3/42Issue resolution89% of issues closed
7.3/30PR acceptance122/498 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 7/21 approved changesets -- score normalized to 3
Inputs used
merged_prs122
open_issues143
closed_issues1,131
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.888
closed_unmerged_prs376
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
16.4/25Owner reach187 followers of gruntjs
25/25Track record68 public repos, account ~14 yr old
Inputs used
followers187
owner_typeOrganization
is_verifiedno
owner_logingruntjs
public_repos68
account_age_days5,254

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 33 days ago
20/20Version history73 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgrunt
ecosystemsnpm
any_deprecatedno
min_days_since_publish33

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests3 out of 12 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttp://gruntjs.com/
10/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicshacktoberfest
has_wikiyes
homepagehttp://gruntjs.com/
docs_sitehttp://gruntjs.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.5/2.5CI-Tests3 out of 12 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 7/21 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 60 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages97
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:grunt@1.6.3 runtime dependency closure — what installing the published package pulls in — 97 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.9/40Legible commit history41 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.41
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/37 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes42,447
source_files_sampled37
oversized_source_files0

Key facts

12,239GitHub stars
78contributors
13commits, last 12 months
16days since last push
12releases
1bus factor
143open 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 ★ / 1,489 ⇿
0Stars
1,489Forks
12Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

05001,0001,5001,489142013-092020-022026-07
Major 0Minor 6Patch 6

Each point covers 12 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-08-30 16:51 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
2CI-Tests3 out of 12 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 7/21 approved changesets -- score normalized to 3
10Contributorsproject has 60 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
npmdateformat~4.6.2package.json
npmeventemitter2~0.4.13package.json
npmexit~0.1.2package.json
npmfindup-sync~5.0.0package.json
npmglob~7.1.6package.json
npmgrunt-cli^1.4.3package.json
npmgrunt-known-options~2.0.0package.json
npmgrunt-legacy-log~3.0.0package.json
npmgrunt-legacy-util~2.0.1package.json
npmiconv-lite~0.6.3package.json
npmjs-yaml^3.15.0package.json
npmminimatch^3.1.5package.json
npmnopt^5.0.0package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmdateformat~4.6.2direct
npmeventemitter2~0.4.13direct
npmexit~0.1.2direct
npmfindup-sync~5.0.0direct
npmglob~7.1.6direct
npmgrunt-cli^1.4.3direct
npmgrunt-known-options~2.0.0direct
npmgrunt-legacy-log~3.0.0direct
npmgrunt-legacy-util~2.0.1direct
npmiconv-lite~0.6.3direct
npmjs-yaml^3.15.0direct
npmminimatch^3.1.5direct
npmnopt^5.0.0direct
npmdifflet~1.0.1indirect
npmeslint^8.57.0indirect
npmeslint-config-grunt^2.0.1indirect
npmeslint-plugin-pabigot^1.1.0indirect
npmqunit^2.25.0indirect
npmtemporary~1.1.0indirect
npmthrough2~4.0.2indirect
Dependency advisories 0

Installing npm:grunt@1.6.3 pulls in 97 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 statisticsnpm.