Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 10:30 UTC

emarsden / pssh-box-rs

Parsing and serialization support for PSSH boxes used in DRM systems

RustMIT★ 16 stars⑂ 1 forksince Jan 2024View on GitHub ↗

emarsden/pssh-box-rs holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (71/100) and lowest on Community & Adoption (40/100). It was last updated 51 days ago. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

Eric MarsdenPersonal account
82 followers23 public repossince Nov 2009

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iopssh-box0.2.53,0831851 days agocontentprotectiondashdrmpsshstreamingparser-implementations

Metrics by category

Vitality

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

57Moderate · 21% of overall
How it's scored
18/36Push recency — last push 51 days ago
11.8/36Commit cadence — 17/52 weeks with commits
15.1/18Commit volume — 47 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year47
human_commit_share0.99
days_since_last_push51
active_weeks_last_year17
How it's scored
16.2/27Ships releases — 16 version tags (no GitHub releases)
27/36Release recency — latest release 168 days ago
19.8/27Release cadence — a release every ~68.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv0.2.4
releases_from_tagsyes
days_since_latest_release168
mean_days_between_releases68.2
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?

40Weak · 17% of overall
How it's scored
19.1/60Stars — 16 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars16
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
46.5/80Monthly downloads — 3,083 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespssh-box
dependents—
ecosystemscrates
total_downloads54,182
monthly_downloads3,083
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
6/30PR acceptance — 1/5 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/28 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs4
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
13.8/25Owner reach — 82 followers of emarsden
22.1/25Track record — 23 public repos, account ~16 yr old
Inputs used
followers82
owner_typeUser
is_verified—
owner_loginemarsden
public_repos23
account_age_days6,152
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 51 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespssh-box
ecosystemscrates
any_deprecatedno
min_days_since_publish51

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 1 out of 1 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/pssh-box
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsdrm, playready, pssh, widevine
has_wikiyes
homepage—
docs_sitehttps://docs.rs/pssh-box
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 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
2.5/2.5CI-Tests — 1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/28 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): 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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
4.3/40Legible commit history — 8 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.081
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — .justfile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files.justfile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/15 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes48,252
source_files_sampled15
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — src/widevine_pssh_data.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filessrc/widevine_pssh_data.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

16GitHub stars
1contributors
47commits, last 12 months
51days since last push
16releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-13 10:30 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/28 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
crates.ioserde1.0.229Cargo.toml
crates.ioserde_path_to_error0.1.20Cargo.toml
crates.ioserde_with3.21.0Cargo.toml
crates.ioserde-xml-rs0.8.2Cargo.toml
crates.ioserde_json1.0.151Cargo.toml
crates.iozerocopy0.8.55Cargo.toml
crates.ioquick-xml0.41.0Cargo.toml
crates.ioprost0.14.4Cargo.toml
crates.ioprost-types0.14.4Cargo.toml
crates.iobytes1.12.1Cargo.toml
crates.iobyteorder1.5.0Cargo.toml
crates.iohex0.4.3Cargo.toml
crates.iohex-literal1.1.0Cargo.toml
crates.iohxdmp0.2.1Cargo.toml
crates.iobstr1.13.0Cargo.toml
crates.ionum_enum0.7.6Cargo.toml
crates.iobase640.23.0Cargo.toml
crates.iotracing0.1.44Cargo.toml
crates.ioanyhow1.0.104Cargo.toml
All dependencies 28

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

RegistryPackageVersionRelation
crates.ioanyhow—direct
crates.iobase64—direct
crates.iobstr—direct
crates.iobyteorder—direct
crates.iobytes—direct
crates.iohex—direct
crates.iohex-literal—direct
crates.iohxdmp—direct
crates.ionum_enum—direct
crates.ioprost—direct
crates.ioprost-types—direct
crates.ioquick-xml—direct
crates.ioserde—direct
crates.ioserde-xml-rs—direct
crates.ioserde_json—direct
crates.ioserde_path_to_error—direct
crates.ioserde_with—direct
crates.iotracing—direct
crates.iozerocopy—direct
crates.ioclap—indirect
crates.iopretty_assertions—indirect
crates.ioprost-build—indirect
crates.ioprotobuf-src—indirect
crates.ioprotox—indirect
crates.ioreqwest—indirect
crates.iotest-log—indirect
crates.iotokio—indirect
crates.iotracing-subscriber—indirect
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 statistics — crates.io.