Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-30 22:22 UTC

aresponses / aresponses

Asyncio http mocking. Similar to the responses library used for 'requests'

PythonMIT★ 107 stars⑂ 20 forkssince Sep 2017View on GitHub ↗

aresponses/aresponses holds a health index of 25 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (58/100) and lowest on Vitality (13/100). It was last updated 749 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

aresponsesOrganization
0 followers1 public reposince Jan 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIaresponses3.0.0107,36425930 days agoasynciotestingresponses

Metrics by category

Vitality

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

13Critical · 21% of overall
How it's scored
0/36Push recency — last push 749 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 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_year0
human_commit_share1
days_since_last_push749
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 22 version tags (no GitHub releases)
0/36Release recency — latest release 930 days ago
12.6/27Release cadence — a release every ~155.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count22
latest_release_tag3.0.0
releases_from_tagsyes
days_since_latest_release930
mean_days_between_releases155.4
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?

58Moderate · 17% of overall
How it's scored
32.9/60Stars — 107 stars
10.7/25Forks — 20 forks
6.4/15Watchers — 15 watchers
Inputs used
forks20
stars107
watchers15
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
67.1/80Monthly downloads — 107,364 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesaresponses
dependents
ecosystemspypi
total_downloads
monthly_downloads107,364
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.1/22.5Commit distribution — top contributor authored 82% of commits
13.5/13.5Contributor breadth — 14 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.819
How it's scored
38.5/42Issue resolution — 92% of issues closed
25.1/30PR acceptance — 41/49 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 6/22 approved changesets -- score normalized to 2
Inputs used
merged_prs41
open_issues3
closed_issues33
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.917
closed_unmerged_prs8
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 backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of aresponses
13.3/25Track record — 1 public repos, account ~5 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_loginaresponses
public_repos1
account_age_days2,025
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
4/35Publish recency — latest publish 930 days ago
20/20Version history — 25 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaresponses
ecosystemspypi
any_deprecatedno
min_days_since_publish930

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 6/22 approved changesets -- score normalized to 2
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not 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
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
0/7.5Vulnerabilities — 45 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): branch_protection, packaging, 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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages15
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:aresponses@3.0.0 runtime dependency closure — what installing the published package pulls in — 15 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 78 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.78
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
0/11Static type checking
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_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/10 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes13,177
source_files_sampled10
oversized_source_files0

Key facts

107GitHub stars
14contributors
0commits, last 12 months
749days since last push
22releases
1bus factor
3open 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 ★ / 20 ⇿
0Stars
20Forks
14Releases

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.

0481216202012018-042022-052026-05
Major 3Minor 2Patch 9

Each point covers 8 days.

OpenSSF Scorecard 2.6 / 10
2.6aggregate

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-30 22:21 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
0CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/22 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Vulnerabilities45 existing vulnerabilities detected
All dependencies 85

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

RegistryPackageVersionRelation
PyPIaiohttpindirect
PyPIaiohttp3.8.1indirect
PyPIaiohttp3.8.6indirect
PyPIaiosignal1.2.0indirect
PyPIaiosignal1.3.1indirect
PyPIasync-timeout4.0.2indirect
PyPIasync-timeout4.0.3indirect
PyPIasynctest0.13.0indirect
PyPIattrs21.4.0indirect
PyPIattrs23.2.0indirect
PyPIblack23.3.0indirect
PyPIcharset-normalizer2.0.10indirect
PyPIcharset-normalizer3.3.2indirect
PyPIclick8.1.7indirect
PyPIcoverage6.3indirect
PyPIcoverage7.2.7indirect
PyPIeradicate2.0.0indirect
PyPIeradicate2.3.0indirect
PyPIexceptiongroup1.2.0indirect
PyPIflake84.0.1indirect
PyPIflake85.0.4indirect
PyPIflake8-builtins1.5.3indirect
PyPIflake8-builtins2.1.0indirect
PyPIflake8-comprehensions3.13.0indirect
PyPIflake8-comprehensions3.8.0indirect
PyPIflake8-eradicate1.2.0indirect
PyPIflake8-eradicate1.4.0indirect
PyPIflake8-mutable1.2.0indirect
PyPIflake8-plugin-utils1.3.2indirect
PyPIflake8-plugin-utils1.3.3indirect
PyPIflake8-polyfill1.0.2indirect
PyPIflake8-printf-formatting1.1.2indirect
PyPIflake8-pytest-style1.6.0indirect
PyPIflake8-pytest-style1.7.2indirect
PyPIflake8-use-fstring1.3indirect
PyPIflake8-use-fstring1.4indirect
PyPIflake8-variables-names0.0.4indirect
PyPIflake8-variables-names0.0.6indirect
PyPIfrozenlist1.3.0indirect
PyPIfrozenlist1.3.3indirect
PyPIidna3.3indirect
PyPIidna3.6indirect
PyPIimportlib-metadata4.10.1indirect
PyPIimportlib-metadata4.2.0indirect
PyPIiniconfig1.1.1indirect
PyPIiniconfig2.0.0indirect
PyPImccabe0.6.1indirect
PyPImccabe0.7.0indirect
PyPImultidict6.0.2indirect
PyPImultidict6.0.4indirect
PyPImypy-extensions1.0.0indirect
PyPIpackaging21.3indirect
PyPIpackaging23.2indirect
PyPIpathspec0.11.2indirect
PyPIpep8-naming0.12.1indirect
PyPIpep8-naming0.13.3indirect
PyPIplatformdirs4.0.0indirect
PyPIpluggy1.0.0indirect
PyPIpluggy1.2.0indirect
PyPIpy1.11.0indirect
PyPIpycodestyle2.8.0indirect
PyPIpycodestyle2.9.1indirect
PyPIpyflakes2.4.0indirect
PyPIpyflakes2.5.0indirect
PyPIpyparsing3.0.7indirect
PyPIpytest6.2.5indirect
PyPIpytest7.4.4indirect
PyPIpytest-asyncioindirect
PyPIpytest-asyncio0.16.0indirect
PyPIpytest-asyncio0.17.2indirect
PyPIpytest-asyncio0.21.1indirect
PyPIpytest-cov3.0.0indirect
PyPIpytest-cov4.1.0indirect
PyPIpytest-randomly3.11.0indirect
PyPIpytest-randomly3.12.0indirect
PyPItoml0.10.2indirect
PyPItomli2.0.0indirect
PyPItomli2.0.1indirect
PyPItyped-ast1.5.5indirect
PyPItyping-extensions4.0.1indirect
PyPItyping-extensions4.7.1indirect
PyPIyarl1.7.2indirect
PyPIyarl1.9.4indirect
PyPIzipp3.15.0indirect
PyPIzipp3.7.0indirect
Dependency advisories 0

Installing pypi:aresponses@3.0.0 pulls in 15 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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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