Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 21:53 UTC

tobgu / pyrsistent

Persistent/Immutable/Functional data structures for Python

Python · CMIT★ 2,200 stars⑂ 169 forkssince Jun 2013View on GitHub ↗

tobgu/pyrsistent holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (76/100) and lowest on Vitality (32/100). It was last updated 222 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Tobias GustafssonPersonal account
87 followers36 public repossince Nov 2010

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 publish
PyPIpyrsistent0.20.029,539,367751051 days ago

Metrics by category

Vitality

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

32At Risk · 21% of overall
How it's scored
3.6/36Push recency — last push 222 days ago
4.8/36Commit cadence — 7/52 weeks with commits
11.7/18Commit volume — 19 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_year19
human_commit_share1
days_since_last_push222
active_weeks_last_year7
How it's scored
16.2/27Ships releases — 75 version tags (no GitHub releases)
16.2/36Release recency — latest release 242 days ago
12.6/27Release cadence — a release every ~216.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count75
latest_release_tagv0.21.0
releases_from_tagsyes
days_since_latest_release242
mean_days_between_releases216.7
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?

75Good · 17% of overall
How it's scored
54.2/60Stars — 2,200 stars
18.5/25Forks — 169 forks
8.4/15Watchers — 34 watchers
Inputs used
forks169
stars2,200
watchers34
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 29,539,367 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespyrsistent
dependents—
ecosystemspypi
total_downloads—
monthly_downloads29,539,367
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.3/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 67 contributors
10/10OpenSSF Scorecard: Contributors — project has 41 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled67
top_contributor_share0.766
How it's scored
35/42Issue resolution — 83% of issues closed
24.8/30PR acceptance — 110/133 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 10/21 approved changesets -- score normalized to 4
Inputs used
merged_prs110
open_issues31
closed_issues156
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.834
closed_unmerged_prs23
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
14/25Owner reach — 87 followers of tobgu
23.4/25Track record — 36 public repos, account ~15 yr old
Inputs used
followers87
owner_typeUser
is_verified—
owner_logintobgu
public_repos36
account_age_days5,776
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
4/35Publish recency — latest publish 1,051 days ago
20/20Version history — 75 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespyrsistent
ecosystemspypi
any_deprecatedno
min_days_since_publish1,051

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 3 out of 10 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsimmutable, datastructures, python, functional
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 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.8/2.5CI-Tests — 3 out of 10 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 10/21 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 41 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
5/5Fuzzing — project is 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
5/5Packaging — packaging workflow detected
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
0/7.5Vulnerabilities — 30 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories36
affected_packages6
assessed_packages25
unassessed_packages10
affected_by_severityhigh 4, moderate 1, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 25 resolved dependencies against OSV. 10 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://tox.readthedocs.io/llms.txt)
22.4/40Legible commit history — 42 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://tox.readthedocs.io/llms.txt
legible_history_share0.42
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
11/11Static type checking — pyrsistent/py.typed
0/10Reproducible environment
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_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configspyrsistent/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (pyrsistent/py.typed)
55/55Manageable file sizes — 0/43 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes49,806
source_files_sampled43
oversized_source_files0

Key facts

2,200GitHub stars
67contributors
19commits, last 12 months
222days since last push
75releases
1bus factor
31open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 169 ⇿
0Stars
169Forks
67Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0408012016020016542014-112020-102026-09
Major 0Minor 15Patch 52

Each point covers 11 days.

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-10 21:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests3 out of 10 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/21 approved changesets -- score normalized to 4
10Contributorsproject has 41 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities30 existing vulnerabilities detected
All dependencies 35

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

RegistryPackageVersionRelation
PyPIalabaster0.7.13indirect
PyPIbabel2.13.0indirect
PyPIcertifi2023.7.22indirect
PyPIcharset-normalizer3.3.0indirect
PyPIdocutils0.18.1indirect
PyPIhypothesis—indirect
PyPIidna3.4indirect
PyPIimagesize1.4.1indirect
PyPIjinja23.1.2indirect
PyPImarkupsafe2.1.3indirect
PyPImemory-profiler0.57.0indirect
PyPIpackaging23.2indirect
PyPIpip—indirect
PyPIpip-tools—indirect
PyPIpsutil5.7.0indirect
PyPIpygments2.16.1indirect
PyPIpyperform—indirect
PyPIpytest—indirect
PyPIrequests2.31.0indirect
PyPIsetuptools—indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsphinx—indirect
PyPIsphinx7.2.6indirect
PyPIsphinx-rtd-theme—indirect
PyPIsphinx-rtd-theme1.3.0indirect
PyPIsphinxcontrib-applehelp1.0.7indirect
PyPIsphinxcontrib-devhelp1.0.5indirect
PyPIsphinxcontrib-htmlhelp2.0.4indirect
PyPIsphinxcontrib-jquery4.1indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.6indirect
PyPIsphinxcontrib-serializinghtml1.1.9indirect
PyPItox—indirect
PyPItwine—indirect
PyPIurllib32.0.7indirect
Dependency advisories 6

This repository publishes no package the index resolves, so its own dependency graph was assessed — 25 packages, which also include development and test pins that never ship: 6 carry known advisories, of which 0 are direct. 10 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2023.7.22indirecthigh22024.7.4
idna3.4indirecthigh43.15
jinja23.1.2indirecthigh103.1.6
urllib32.0.7indirecthigh122.7.0
requests2.31.0indirectmoderate62.33.0
pygments2.16.1indirectlow22.20.0

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.

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 — PyPI.