Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 00:12 UTC

pytest-dev / pluggy

A minimalist production ready plugin system

PythonMIT★ 1,665 stars⑂ 152 forkssince Apr 2015View on GitHub ↗

pytest-dev/pluggy holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (65/100). It was last updated 2 days ago. 3 contributors account for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

pytest-devOrganization
796 followers78 public repossince Sep 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIpluggy1.6.0-24427 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
33.9/36Commit cadence49/52 weeks with commits
18/18Commit volume125 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year125
human_commit_share
days_since_last_push2
active_weeks_last_year49
How it's scored
16.2/27Ships releases24 version tags (no GitHub releases)
7.2/36Release recencylatest release 427 days ago
12.6/27Release cadencea release every ~242.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count24
latest_release_tag1.6.0
releases_from_tagsyes
days_since_latest_release427
mean_days_between_releases242.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?

65Good · 17% of overall
How it's scored
52.3/60Stars1,665 stars
18.2/25Forks152 forks
7.1/15Watchers20 watchers
Inputs used
forks152
stars1,665
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/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_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

83Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
17.8/22.5Commit distributiontop contributor authored 21% of commits
13.5/13.5Contributor breadth52 contributors
10/10OpenSSF Scorecard: Contributorsproject has 87 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled52
top_contributor_share0.211
How it's scored
34.6/42Issue resolution82% of issues closed
26.3/30PR acceptance423/483 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 2/3 approved changesets -- score normalized to 6
Inputs used
merged_prs423
open_issues33
closed_issues156
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.825
closed_unmerged_prs60
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
20.9/25Owner reach796 followers of pytest-dev
25/25Track record78 public repos, account ~11 yr old
Inputs used
followers796
owner_typeOrganization
is_verified
owner_loginpytest-dev
public_repos78
account_age_days4,313
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
14/35Publish recencylatest publish 427 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespluggy
ecosystemspypi
any_deprecatedno
min_days_since_publish427

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configtox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://pluggy.readthedocs.io/en/latest/
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicshooks, python
has_wikino
homepagehttps://pluggy.readthedocs.io/en/latest/
docs_sitehttps://pluggy.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 2/3 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 87 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
3/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.5
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.

79Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes2,051
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configtox.ini
11/11Static type checkingsrc/pluggy/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
6/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configssrc/pluggy/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (src/pluggy/py.typed)
55/55Manageable file sizes0/30 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes27,245
source_files_sampled30
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples, recipes
Inputs used
example_dirsexamples, recipes
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

1,665GitHub stars
52contributors
125commits, last 12 months
2days since last push
24releases
3bus factor
33open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 7.5 / 10
7.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-07-17 00:11 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 2/3 approved changesets -- score normalized to 6
10Contributorsproject has 87 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 32

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

RegistryPackageVersionRelation
PyPIcachetools7.0.6indirect
PyPIcfgv3.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.5indirect
PyPIdistlib0.4.0indirect
PyPIeggsampleindirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock3.29.0indirect
PyPIidentify2.6.19indirect
PyPIiniconfig2.3.0indirect
PyPInodeenv1.10.0indirect
PyPIpackaging26.2indirect
PyPIplatformdirs4.9.6indirect
PyPIpluggyindirect
PyPIpre-commit4.6.0indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpygmentsindirect
PyPIpygments2.20.0indirect
PyPIpyproject-api1.10.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-benchmark5.2.3indirect
PyPIpython-discovery1.2.2indirect
PyPIpyyaml6.0.3indirect
PyPIsetuptoolsindirect
PyPIsetuptools-scmindirect
PyPIsphinxindirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItowncrierindirect
PyPItox4.53.0indirect
PyPItyping-extensions4.15.0indirect
PyPIvirtualenv21.3.0indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.