Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 11:54 UTC

divriots / sharp-libvips

Packaging scripts to prebuild libvips and its dependencies - you're probably looking for https://github.com/lovell/sharp

Shell · DockerfileApache-2.0★ 0 stars⑂ 0 forkssince Apr 2026forkView on GitHub ↗

divriots/sharp-libvips holds a health index of 25 out of 100, placing it in the At Risk band. It scores highest on Vitality (47/100) and lowest on Community & Adoption (12/100). It was last updated 40 days ago. A single contributor accounts for most of its recent work.

25
overall / 100
At Risk

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.

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

Ownership

‹div›RIOTSOrganization
271 followers87 public repossince Nov 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@img/sharp-libvips-devpoints to another repo — not scored1.3.460,0754821 days ago
npm@img/sharp-libvips-linux-armpoints to another repo — not scored1.3.411,607,7934921 days ago
npm@img/sharp-libvips-linux-x64points to another repo — not scored1.3.4402,119,5344721 days ago
npm@img/sharp-libvips-win32-x64points to another repo — not scored1.3.425,7144521 days ago
npm@img/sharp-libvips-darwin-x64points to another repo — not scored1.3.416,742,0814621 days ago
npm@img/sharp-libvips-dev-wasm32points to another repo — not scored1.3.417,9804621 days ago
npm@img/sharp-libvips-win32-ia32points to another repo — not scored1.3.418,3424521 days ago
npm@img/sharp-libvips-linux-arm64points to another repo — not scored1.3.434,531,2744721 days ago

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
18/36Push recency — last push 40 days ago
12.5/36Commit cadence — 18/52 weeks with commits
16.7/18Commit volume — 71 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_year71
human_commit_share0.81
days_since_last_push40
active_weeks_last_year18
How it's scored
16.2/27Ships releases — 90 version tags (no GitHub releases)
7.2/36Release recency — latest release 562 days ago
19.8/27Release cadence — a release every ~57.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count90
latest_release_tagv8.16.1
releases_from_tagsyes
days_since_latest_release562
mean_days_between_releases57.5
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?

12Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

37Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.6/22.5Commit distribution — top contributor authored 75% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.751
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17.5/25Owner reach — 271 followers of divriots
25/25Track record — 87 public repos, account ~7 yr old
Inputs used
followers271
owner_typeOrganization
is_verifiedno
owner_logindivriots
public_repos87
account_age_days2,895

Engineering Quality

Are baseline engineering and documentation practices in place?

18Critical · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

1Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeno
has_docs_dirno
has_descriptionno

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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file 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
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. 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.

13Critical · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
24.4/40Legible commit history — 37 of 81 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.457
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Shell without a type-check config
0/55Manageable file sizes — no source files detected
Inputs used
primary_languageShell
largest_source_bytes—
source_files_sampled0
oversized_source_files0
Excluded from scoring (no data or not applicable): Manageable file sizes. Remaining weights renormalized.

Key facts

0GitHub stars
10contributors
71commits, last 12 months
40days since last push
90releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • Could not fetch npm package '@img/sharp-libvips' from its registry
  • npm package '@img/sharp-libvips-dev' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-linux-arm' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-linux-x64' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-win32-x64' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-darwin-x64' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-dev-wasm32' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-win32-ia32' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • npm package '@img/sharp-libvips-linux-arm64' points at a different repository (https://github.com/lovell/sharp-libvips); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

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-10-19 11:54 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
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
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
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.

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.