Public recordModerate
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 18:37 UTC
gripsack-dev / gripsack
Personal environment manager — packages and dotfiles in one repo, with generations and rollback. Typed Python/TypeScript config, Rust core; no daemon, root, or /nix.
gripsack-dev/gripsack holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (88/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.
62
overall / 100Software 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.
62
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)
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 58 is calibrated to 62 on the published index scale (record calibration 2026-08-02).
Ownership
gripsack-devOrganization
0 followers10 public repossince Aug 2026
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| PyPI | gripsack | 0.16.4 | 3,111 | 36 | 0 days ago | dotfilesenvironmentpackage-manager |
| npm | @gripsack/core | 0.16.4 | 2,099 | 17 | 0 days ago | dotfilespackage-managerenvironment |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
69
Development activity
55Moderate
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 0.7/36 | Commit cadence — 1/52 weeks with commits |
| 18/18 | Commit volume — 178 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully |
Inputs used
| commits_last_year | 178 |
| human_commit_share | 0.92 |
| days_since_last_push | 0 |
| active_weeks_last_year | 1 |
Release discipline
90Excellent
How it's scored
| 27/27 | Ships releases — 84 releases published |
| 36/36 | Release recency — latest release 0 days ago |
| 27/27 | Release cadence — a release every ~0.1 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases. |
Inputs used
| releases_count | 84 |
| latest_release_tag | ts-v0.16.4 |
| releases_from_tags | no |
| days_since_latest_release | 0 |
| mean_days_between_releases | 0.1 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
33
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 1 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 1 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
50Moderate
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 7 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | github.com, shields.io |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
62Moderate
How it's scored
| 49.6/80 | Monthly downloads — 5,210 downloads/month across npm, pypi |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | gripsack, @gripsack/core |
| dependents | — |
| ecosystems | npm, pypi |
| total_downloads | — |
| monthly_downloads | 5,210 |
| 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?
45
Maintainer resilience (bus factor)
16Critical
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
How it's scored
| 0/42 | Issue resolution — 0% of issues closed |
| 30/30 | PR acceptance — 47/47 decided PRs merged |
| 13/13 | Newcomer PR acceptance — 30/30 first-time contributors' PRs merged in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/21 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 47 |
| open_issues | 9 |
| closed_issues | 0 |
| prs_merged_7d | 30 |
| prs_decided_7d | 30 |
| prs_merged_30d | 30 |
| prs_decided_30d | 30 |
| issue_closed_ratio | 0 |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | 1 |
| first_time_prs_merged_30d | 30 |
| first_time_prs_decided_30d | 30 |
Ownership & stewardship
38Weak
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 0/25 | Owner reach — 0 followers of gripsack-dev |
| 7.6/25 | Track record — 10 public repos, account ~0 yr old |
Inputs used
| followers | 0 |
| owner_type | Organization |
| is_verified | no |
| owner_login | gripsack-dev |
| public_repos | 10 |
| account_age_days | 6 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 2 package(s) on npm, pypi |
| 35/35 | Publish recency — latest publish 0 days ago |
| 20/20 | Version history — 36 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | gripsack, @gripsack/core |
| ecosystems | npm, pypi |
| any_deprecated | no |
| min_days_since_publish | 0 |
Engineering Quality
Are baseline engineering and documentation practices in place?
88
Engineering practices
80Excellent
How it's scored
| 24/24 | CI workflows — 9 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — ruff.toml |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 16/20 | OpenSSF Scorecard: CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
100Exceptional
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://gripsack.dev |
| 10/10 | Repository description |
| 10/10 | Topics — 10 topics |
| 10/10 | Wiki |
Inputs used
| topics | cli, configuration-management, dev-environment, developer-tools, dotfiles, dotfiles-manager, home-manager, nix, package-manager, rust |
| has_wiki | yes |
| homepage | https://gripsack.dev |
| docs_site | https://gripsack.dev |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
45
Security posture
45Weak
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2/2.5 | CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/21 approved changesets -- score normalized to 0 |
| 1.5/2.5 | Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — project was created within the last 90 days. Please review its contents carefully |
| 5/5 | Packaging — packaging workflow detected |
| 0.5/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — Project has not signed or included provenance with any releases. |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 17 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 1 |
| scorecard_aggregate | 4.5 |
Excluded from scoring (no data or not applicable): Branch-Protection. 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.
79
Agent context & guidance
85Excellent
How it's scored
| 45/45 | Agent instructions — AGENTS.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 79 of 92 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.859 |
| agent_instruction_files | AGENTS.md |
| agent_instruction_max_bytes | 3,779 |
Verify loop (build / test / typecheck)
81Excellent
How it's scored
| 18/18 | One-command bootstrap — crates/griplint/fixtures/mise/bad-choice/mise.toml, crates/griplint/fixtures/mise/clean/mise.toml, crates/griplint/fixtures/mise/env-either/mise.toml, crates/griplint/fixtures/mise/free-form-tools/mise.toml, crates/griplint/fixtures/mise/parse-error/mise.toml, crates/griplint/fixtures/mise/typo-key/mise.toml, crates/griplint/fixtures/mise/unknown-section/mise.toml, crates/griplint/fixtures/mise/version-stale/mise.toml, crates/griplint/fixtures/mise/wrong-type/mise.toml, crates/griplint/packs/mise.toml |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — ruff.toml |
| 11/11 | Static type checking — python/gripsack/py.typed, typescript/tsconfig.json |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 3 of the last 100 commits are automated dependency updates |
| 1/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | Cargo.lock, package-lock.json, uv.lock |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | crates/griplint/fixtures/mise/bad-choice/mise.toml, crates/griplint/fixtures/mise/clean/mise.toml, crates/griplint/fixtures/mise/env-either/mise.toml, crates/griplint/fixtures/mise/free-form-tools/mise.toml, crates/griplint/fixtures/mise/parse-error/mise.toml, crates/griplint/fixtures/mise/typo-key/mise.toml, crates/griplint/fixtures/mise/unknown-section/mise.toml, crates/griplint/fixtures/mise/version-stale/mise.toml, crates/griplint/fixtures/mise/wrong-type/mise.toml, crates/griplint/packs/mise.toml |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | python/gripsack/py.typed, typescript/tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | Cargo.toml, crates/griplint/Cargo.toml, crates/gripsack-config/Cargo.toml, crates/gripsack-exec/Cargo.toml, crates/gripsack-fetch/Cargo.toml, crates/gripsack-ir/Cargo.toml, crates/gripsack-lint/Cargo.toml, crates/gripsack-store/Cargo.toml, crates/gripsack-trace/Cargo.toml, crates/gripsack/Cargo.toml |
| dependency_bot_commit_share | 0.03 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — Rust (statically typed) |
| 54.6/55 | Manageable file sizes — 1/124 source files over 60KB |
Inputs used
| primary_language | Rust |
| largest_source_bytes | 67,099 |
| source_files_sampled | 124 |
| oversized_source_files | 1 |
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) |
| 0/20 | MCP server |
| 40/40 | Runnable examples — demos |
Inputs used
| example_dirs | demos |
| has_mcp_signal | no |
| api_schema_files | — |
| interfaces_expected_of | network-service |
Key facts
1GitHub stars
1contributors
178commits, last 12 months
0days since last push
84releases
1bus factor
9open issues
crates.io, npm, PyPIpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Could not fetch pypi package 'gripsack-e2e' from its registry
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
- deps.dev does not index pypi:gripsack@0.16.4; advisories assessed against the repository dependency graph instead
More detail
OpenSSF Scorecard 4.5 / 10
4.5aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 8 | CI-Tests | 6 out of 7 merged PRs checked by a CI test -- score normalized to 8 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/21 approved changesets -- score normalized to 0 |
| 6 | Contributors | project has 2 contributing companies or organizations -- score normalized to 6 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | project was created within the last 90 days. Please review its contents carefully |
| 10 | Packaging | packaging workflow detected |
| 1 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 1 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| 0 | Signed-Releases | Project has not signed or included provenance with any releases. |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 2
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| PyPI | gripsack | — | e2e/pyproject.toml |
| PyPI | pytest | >=8 | e2e/pyproject.toml |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
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.
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 — PyPI, npm.