Rustynote / asset-builder
assembles and orchestrates your dependencies so you can run them through your asset pipeline.
Rustynote/asset-builder holds a health index of 11 out of 100, placing it in the Critical band. It scores highest on Engineering Quality (33/100) and lowest on Community & Adoption (12/100). It was last updated 2008 days ago. A single contributor accounts for most of its recent work.
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.
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 24 is calibrated to 18 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| npm | asset-builderpoints to another repo — not scored | 2.0.0 | 2,397 | 17 | 2823 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
Work has arrived and nobody has attended to it
Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.
How abandonment is assessedHow it's scored
| 0/36 | Push recency — last push 2,008 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Inputs used
| commits_last_year | 0 |
| human_commit_share | 1 |
| days_since_last_push | 2,008 |
| active_weeks_last_year | 0 |
Release discipline
How it's scored
| 16.2/27 | Ships releases — 19 version tags (no GitHub releases) |
| 0/36 | Release recency — latest release 2,823 days ago |
| 12.6/27 | Release cadence — a release every ~161.3 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 19 |
| latest_release_tag | v2.0.0 |
| releases_from_tags | yes |
| days_since_latest_release | 2,823 |
| mean_days_between_releases | 161.3 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 0/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 | no |
| has_license | no |
| readme_badges | 4 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | ci.appveyor.com, shields.io, travis-ci.org |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 3.9/22.5 | Commit distribution — top contributor authored 82% of commits |
| 13.5/13.5 | Contributor breadth — 14 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 14 |
| top_contributor_share | 0.825 |
Issue & PR responsiveness
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 0/30 | PR acceptance — no decided pull requests or no data |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 0 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Ownership & stewardship
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 6.5/25 | Owner reach — 7 followers of Rustynote |
| 18.9/25 | Track record — 8 public repos, account ~13 yr old |
Inputs used
| followers | 7 |
| owner_type | User |
| is_verified | — |
| owner_login | Rustynote |
| public_repos | 8 |
| account_age_days | 5,091 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 0/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — http://use-asset-builder.austinpray.com |
| 0/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | http://use-asset-builder.austinpray.com |
| docs_site | http://use-asset-builder.austinpray.com |
| has_readme | no |
| has_docs_dir | no |
| has_description | no |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 7 contributing companies or organizations |
| 0/10 | Dangerous-Workflow — no data |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — no SAST tool detected |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 0/7.5 | Vulnerabilities — 76 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 11 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 7 |
| scorecard_aggregate | 2.1 |
Dependency advisories
How it's scored
| 13.4/35 | Direct dependencies free of known advisories — 1 affected: object-path 0.9.2 (high 7.7) |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 33.5/40 | No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,187 days ago |
Inputs used
| source | osv |
| advisories | 3 |
| affected_packages | 1 |
| assessed_packages | 185 |
| unassessed_packages | 0 |
| affected_by_severity | high 1 |
| direct_affected_packages | 1 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 13.9/40 | Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.26 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | package-lock.json |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 0/45 | Type-checkable code — JavaScript without a type-check config |
| 55/55 | Manageable file sizes — 0/7 source files over 60KB |
Inputs used
| primary_language | JavaScript |
| largest_source_bytes | 17,503 |
| source_files_sampled | 7 |
| oversized_source_files | 0 |
Key facts
Data collection warnings
- Community profile unavailable
- npm package 'asset-builder' points at a different repository (https://github.com/austinpray/asset-builder); excluded from ecosystem scoring
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 2.1 / 10
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 |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 7 contributing companies or organizations |
| n/a | Dangerous-Workflow | no workflows found |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | no SAST tool detected |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 0 | Vulnerabilities | 76 existing vulnerabilities detected |
Direct dependencies 5
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | lodash | ^4.17.11 | package.json |
| npm | main-bower-files | ^2.4.0 | package.json |
| npm | minimatch | ^3.0.4 | package.json |
| npm | object-path | ^0.11.0 | package.json |
| npm | traverse | ^0.6.6 | package.json |
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
Dependency advisories 1
Installing npm:asset-builder@2.0.0 pulls in 185 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.
| Package | Version | Relation | Severity | Advisories | Fixed in |
|---|---|---|---|---|---|
| object-path | 0.9.2 | direct | high | 3 | 0.11.8 |
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.
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.