Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 15:47 UTC

risevest / sigil

Icons and Signs for the Rise Design System

TypeScriptApache-2.0★ 0 stars⑂ 0 forkssince Jan 2025View on GitHub ↗

risevest/sigil holds a health index of 39 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (65/100) and lowest on Vitality (20/100). It was last updated 31 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

21 followers32 public repossince Apr 2020

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

Package ecosystems

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
18/36Push recencylast push 31 days ago
4.2/36Commit cadence6/52 weeks with commits
8.6/18Commit volume8 commits in the last year
2/10OpenSSF Scorecard: Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year8
human_commit_share1
days_since_last_push31
active_weeks_last_year6
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

35Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
54.2/80Monthly downloads11,593 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@risemaxi/sigil, @risemaxi/sicily
dependents
ecosystemsnpm
total_downloads
monthly_downloads11,593
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.5/22.5Commit distributiontop contributor authored 53% of commits
13.5/13.5Contributor breadth20 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.534
How it's scored
0/42Issue resolutionno issues or no data
24/30PR acceptance24/30 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 13/30 approved changesets -- score normalized to 4
Inputs used
merged_prs24
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs6
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
9.7/25Owner reach21 followers of risevest
23.1/25Track record32 public repos, account ~6 yr old
Inputs used
followers21
owner_typeOrganization
is_verifiedno
owner_loginrisevest
public_repos32
account_age_days2,341

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on npm
35/35Publish recencylatest publish 31 days ago
20/20Version history41 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@risemaxi/sigil, @risemaxi/sicily
ecosystemsnpm
any_deprecatedno
min_days_since_publish31

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://risevest.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://risevest.com
docs_sitehttps://risevest.com
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-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0.5/2.5CI-Tests3 out of 13 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
3/7.5Code-ReviewFound 13/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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
1.5/7.5Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
5/5Packagingpackaging workflow detected
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities55 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.26
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingpackages/sicily/tsconfig.json, packages/sigil/tsconfig.json
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
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_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/sicily/tsconfig.json, packages/sigil/tsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes4/12,890 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes201,764
source_files_sampled12,890
oversized_source_files4

Key facts

0GitHub stars
20contributors
8commits, last 12 months
31days since last push
0releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

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).Scorecard v5.5.0 · 2026-09-18 15:46 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests3 out of 13 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 13/30 approved changesets -- score normalized to 4
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
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities55 existing vulnerabilities detected
All dependencies 14

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

RegistryPackageVersionRelation
npm@biomejs/biome^1.9.2indirect
npm@svgr/core^8.1.0indirect
npm@svgr/plugin-jsx^8.1.0indirect
npm@svgr/plugin-svgo^8.1.0indirect
npm@types/bun^1.2.22indirect
npm@types/react^19.1.13indirect
npm@types/react^19.1.14indirect
npmcamelcase^6.0.0indirect
npmcheerio^1.0.0indirect
npmglob^7.1.6indirect
npmreact*indirect
npmreact-native-svg^15.11.1indirect
npmtypescript^5.9.2indirect
npmuppercamelcase^3.0.0indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.