Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 03:50 UTC

pytest-dev / pytest-bdd

BDD library for the pytest runner

PythonMIT★ 1,457 stars⑂ 244 forkssince Mar 2013View on GitHub ↗

pytest-dev/pytest-bdd holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (100/100) and lowest on AI Readiness (56/100). It was last updated today. A single contributor accounts for most of its recent work.

88
overall / 100
Excellent

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.

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

Ownership

pytest-devOrganization
798 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
PyPIpytest-bdd8.1.0-106592 days ago

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
3.5/36Commit cadence5/52 weeks with commits
14.7/18Commit volume42 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year42
human_commit_share
days_since_last_push0
active_weeks_last_year5
How it's scored
16.2/27Ships releases96 version tags (no GitHub releases)
7.2/36Release recencylatest release 592 days ago
19.8/27Release cadencea release every ~84.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count96
latest_release_tag8.1.0
releases_from_tagsyes
days_since_latest_release592
mean_days_between_releases84.6
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?

76Good · 17% of overall
How it's scored
51.3/60Stars1,457 stars
19.9/25Forks244 forks
9.8/15Watchers59 watchers
Inputs used
forks244
stars1,457
watchers59
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
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?

72Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11.2/22.5Commit distributiontop contributor authored 50% of commits
13.5/13.5Contributor breadth59 contributors
10/10OpenSSF Scorecard: Contributorsproject has 19 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled59
top_contributor_share0.503
How it's scored
35/42Issue resolution83% of issues closed
22/30PR acceptance305/416 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 9/11 approved changesets -- score normalized to 8
Inputs used
merged_prs305
open_issues60
closed_issues299
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.833
closed_unmerged_prs111
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 reach798 followers of pytest-dev
25/25Track record78 public repos, account ~11 yr old
Inputs used
followers798
owner_typeOrganization
is_verified
owner_loginpytest-dev
public_repos78
account_age_days4,317
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 592 days ago
20/20Version history106 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespytest-bdd
ecosystemspypi
any_deprecatedno
min_days_since_publish592

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configtox.ini
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://pytest-bdd.readthedocs.io/en/latest/
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsbdd, bdd-framework, pytest-plugin, python, python3, testing
has_wikiyes
homepagehttps://pytest-bdd.readthedocs.io/en/latest/
docs_sitehttps://pytest-bdd.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?

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests17 out of 17 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
6/7.5Code-ReviewFound 9/11 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 19 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.5Maintained23 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
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-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.3
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages12
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:pytest-bdd@8.1.0 runtime dependency closure — what installing the published package pulls in — 12 packages. 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format configtox.ini
11/11Static type checkingsrc/pytest_bdd/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/pytest_bdd/py.typed
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
27/45Type-checkable codePython with type-check config (src/pytest_bdd/py.typed)
55/55Manageable file sizes0/68 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes42,223
source_files_sampled68
oversized_source_files0

Key facts

1,457GitHub stars
59contributors
42commits, last 12 months
0days since last push
96releases
1bus factor
60open issues
PyPIpackage ecosystems

More detail

Star and fork history 1,457 ★ / 0 ⇿
1,457Stars

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

05001,0001,5001,457122019-062022-122026-07

Each point covers 7 days.

OpenSSF Scorecard 6.3 / 10
6.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-07-21 03:50 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 9/11 approved changesets -- score normalized to 8
10Contributorsproject has 19 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
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
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIMakopyproject.toml
PyPIparsepyproject.toml
PyPIparse-typepyproject.toml
PyPIpytest>=7.0.0pyproject.toml
PyPItyping-extensionspyproject.toml
PyPIpackagingpyproject.toml
PyPIgherkin-official>=29.0.0,!=31.0.0,!=32.0.0pyproject.toml
All dependencies 82

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

RegistryPackageVersionRelation
PyPIgherkin-official37.0.0direct
PyPImako1.3.12direct
PyPIpackaging25.0direct
PyPIparse1.20.2direct
PyPIparse-type0.6.6direct
PyPIpytest9.1.1direct
PyPItyping-extensions4.15.0direct
PyPIalabaster0.7.16indirect
PyPIanyio4.12.0indirect
PyPIbabel2.17.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIbuild1.3.0indirect
PyPIcachetools6.2.2indirect
PyPIcertifi2025.11.12indirect
PyPIcffi2.0.0indirect
PyPIchardet5.2.0indirect
PyPIcharset-normalizer3.4.4indirect
PyPIclick8.3.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.12.0indirect
PyPIcryptography49.0.0indirect
PyPIdistlib0.4.0indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.3.1indirect
PyPIexecnet2.1.2indirect
PyPIfilelock3.29.4indirect
PyPIh110.16.0indirect
PyPIid1.5.0indirect
PyPIidna3.15indirect
PyPIimagesize1.4.1indirect
PyPIimportlib-metadata8.7.0indirect
PyPIiniconfig2.3.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.0.1indirect
PyPIjaraco-functools4.3.0indirect
PyPIjeepney0.9.0indirect
PyPIjinja23.1.6indirect
PyPIkeyring25.7.0indirect
PyPIlibrt0.7.2indirect
PyPImarkdown-it-py4.0.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImore-itertools10.8.0indirect
PyPImypy1.19.0indirect
PyPImypy-extensions1.1.0indirect
PyPInh30.3.2indirect
PyPIpathspec0.12.1indirect
PyPIplatformdirs4.5.1indirect
PyPIpluggy1.6.0indirect
PyPIpycparser2.23indirect
PyPIpygments2.20.0indirect
PyPIpyproject-api1.10.0indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIreadme-renderer44.0indirect
PyPIrequests2.34.2indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrfc39862.0.0indirect
PyPIrich14.2.0indirect
PyPIsecretstorage3.5.0indirect
PyPIsix1.17.0indirect
PyPIsnowballstemmer3.0.1indirect
PyPIsphinx7.4.7indirect
PyPIsphinx-autobuild2024.10.3indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIstarlette1.3.1indirect
PyPItomli2.3.0indirect
PyPItox4.32.0indirect
PyPItwine6.2.0indirect
PyPItypes-setuptools80.9.0.20250822indirect
PyPIurllib32.7.0indirect
PyPIuvicorn0.38.0indirect
PyPIvirtualenv20.36.1indirect
PyPIwatchfiles1.1.1indirect
PyPIwebsockets15.0.1indirect
PyPIzipp3.23.0indirect
Dependency advisories 0

Installing pypi:pytest-bdd@8.1.0 pulls in 12 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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

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