Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 15:39 UTC

wexample / python-filestate

PythonMIT★ 0 stars⑂ 0 forkssince Jun 2024View on GitHub ↗
KindLibraryhow this is determined

wexample/python-filestate holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (63/100) and lowest on Security (1/100). It was last updated 62 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

wexampleOrganization
1 follower180 public repossince Feb 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIwexample-filestate17.5.22,6241010 days ago

Metrics by category

Vitality

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

35Weak · 21% of overall

Development activity

58Moderate
How it's scored
18/36Push recency — last push 62 days ago
16.6/36Commit cadence — 24/52 weeks with commits
18/18Commit volume — 485 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year485
human_commit_share1
days_since_last_push62
active_weeks_last_year24

Release discipline

1Critical
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

32At Risk · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

57Moderate
How it's scored
45.6/80Monthly downloads — 2,624 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswexample-filestate
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,624
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?

63Moderate · 23% of overall

Maintainer resilience (bus factor)

12Critical
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 — no data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

100Exceptional
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 1/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs1
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, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

57Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of wexample
25/25Track record — 180 public repos, account ~9 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginwexample
public_repos180
account_age_days3,526

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 101 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswexample-filestate
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

34At Risk · 19% of overall

Engineering practices

30At Risk
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-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

40Weak
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

1Critical · 16% of overall

Security posture

1Critical
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

60Moderate · 4% of overall

Agent context & guidance

59Moderate
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 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_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes569

Verify loop (build / test / typecheck)

37Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — src/wexample_filestate/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 — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configssrc/wexample_filestate/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

82Excellent
How it's scored
27/45Type-checkable code — Python with type-check config (src/wexample_filestate/py.typed)
55/55Manageable file sizes — 0/257 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes25,942
source_files_sampled257
oversized_source_files0

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
1contributors
485commits, last 12 months
62days since last push
0releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • deps.dev does not index pypi:wexample-filestate@17.5.2; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/wexample/python-filestate: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-10-22T15:39:02Z. Please include `B8EA:2D0559:8B35083:CA337AF:6ADA2E14` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 13
RegistryPackageVersion constraintManifest
PyPIattrs>=23.1.0pyproject.toml
PyPIcattrs>=23.1.0pyproject.toml
PyPIjinja2—pyproject.toml
PyPIpython-dotenv—pyproject.toml
PyPIruamel.yaml—pyproject.toml
PyPItomlkit—pyproject.toml
PyPIwexample-config>=7.2.0pyproject.toml
PyPIwexample-event>=8.0.0pyproject.toml
PyPIwexample-file>=9.1.0pyproject.toml
PyPIwexample-helpers-yaml>=7.0.0pyproject.toml
PyPIwexample-prompt>=14.1.0pyproject.toml
PyPIwexample-runner>=9.2.0pyproject.toml
PyPIxmltodict—pyproject.toml
All dependencies 10

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

RegistryPackageVersionRelation
PyPIattrs—direct
PyPIcattrs—direct
PyPIwexample-config—direct
PyPIwexample-event—direct
PyPIwexample-file—direct
PyPIwexample-helpers-yaml—direct
PyPIwexample-prompt—direct
PyPIwexample-runner—direct
PyPI16-0-0—indirect
PyPIpytest-benchmark—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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with wexample/python-filestate. Read them side by side →

100onnx/onnxOpen standard for machine learning interoperabilityExceptional100uxlfoundation/oneDNNoneAPI Deep Neural Network Library (oneDNN)Exceptional100scikit-learn/scikit-learnscikit-learn: machine learning in PythonExceptional100zephyrproject-rtos/zephyrPrimary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.Exceptional100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional100astropy/astropyAstronomy and astrophysics core libraryExceptional

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.