Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-15 08:21 UTC

valargroup / ypir

Rust · PythonMIT★ 0 stars⑂ 0 forkssince Mar 2026forkView on GitHub ↗
KindNetwork serviceCommand-line toolLibraryhow this is determined

valargroup/ypir holds a health index of 39 out of 100, placing it in the Weak band. It scores highest on Vitality (75/100) and lowest on Engineering Quality (20/100). It was last updated 2 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

Valar GroupOrganization
12 followers64 public repossince Jan 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iovalar-ypir0.2.02,97062 days ago

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
5.5/36Commit cadence8/52 weeks with commits
15.7/18Commit volume55 commits in the last year
10/10OpenSSF Scorecard: Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year55
human_commit_share1
days_since_last_push2
active_weeks_last_year8
How it's scored
16.2/27Ships releases5 version tags (no GitHub releases)
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~32.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tagv0.2.0
releases_from_tagsyes
days_since_latest_release2
mean_days_between_releases32.1
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?

24At Risk · 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
0/22.5README
22.5/22.5Licenserecognized license (MIT)
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
How it's scored
46.3/80Monthly downloads2,970 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesvalar-ypir
dependents
ecosystemscrates
total_downloads9,647
monthly_downloads2,970
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.4/22.5Commit distributiontop contributor authored 63% of commits
5.4/13.5Contributor breadth4 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.628
How it's scored
0/42Issue resolutionno issues or no data
17.7/30PR acceptance13/22 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 2/8 approved changesets -- score normalized to 2
Inputs used
merged_prs13
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio
closed_unmerged_prs9
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 domainverified-domain status not read for this organization
8/25Owner reach12 followers of valargroup
14.2/25Track record64 public repos, account ~0 yr old
Inputs used
followers12
owner_typeOrganization
is_verified
owner_loginvalargroup
public_repos64
account_age_days213
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 2 days ago
20/20Version history6 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesvalar-ypir
ecosystemscrates
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

20At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

15Critical
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/valar-ypir
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://docs.rs/valar-ypir
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

26At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 2/8 approved changesets -- score normalized to 2
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.9/40Legible commit history51 of 78 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.654
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, demo/client/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentDockerfile, lockfile
5.1/10Demonstrated agent practice2 of the last 78 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_testsyes
lockfilesCargo.lock
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.026
toolchain_manifestsCargo.toml, demo/client/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
51.7/55Manageable file sizes2/33 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes69,319
source_files_sampled33
oversized_source_files2

Key facts

0GitHub stars
4contributors
55commits, last 12 months
2days since last push
5releases
1bus factor
0open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.6 / 10
2.6aggregate

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-15 08:21 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 2/8 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
crates.iospiral-rs0.5Cargo.toml
crates.iorayon1Cargo.toml
crates.iorand0.8.5Cargo.toml
crates.iorand_chacha0.3.1Cargo.toml
crates.ioserde_json1.0Cargo.toml
crates.ioserde1Cargo.toml
crates.iofastrand2Cargo.toml
crates.iolog0.4Cargo.toml
crates.ioenv_logger0.11Cargo.toml
crates.ioclap4Cargo.toml
crates.ioactix-web4Cargo.toml
crates.ioactix-http3.7.0Cargo.toml
crates.ioactix-cors0.7.0Cargo.toml
crates.iofutures0.3Cargo.toml
crates.iobzip20.4.4Cargo.toml
crates.iobase640.22.1Cargo.toml
crates.ioreqwest0.12Cargo.toml
crates.iosha10.10.6Cargo.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.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.