Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 17:34 UTC

apitally / apitally-py

Simple API monitoring & analytics for Python apps

PythonMIT★ 225 stars⑂ 10 forkssince Jul 2023View on GitHub ↗

apitally/apitally-py holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (99/100) and lowest on Community & Adoption (55/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

ApitallyOrganization · verified domain
35 followers12 public repossince Jul 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIapitally0.25.139,0837373 days ago

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 191 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year191
human_commit_share0.12
days_since_last_push0
active_weeks_last_year49

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 69 releases published
36/36Release recency — latest release 73 days ago
27/27Release cadence — a release every ~22.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count69
latest_release_tagv0.25.1
releases_from_tagsno
days_since_latest_release73
mean_days_between_releases22.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?

55Moderate · 17% of overall
How it's scored
38.1/60Stars — 225 stars
8/25Forks — 10 forks
0/15Watchers — 1 watchers
Inputs used
forks10
stars225
watchers1
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
61.2/80Monthly downloads — 39,083 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesapitally
dependents—
ecosystemspypi
total_downloads—
monthly_downloads39,083
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?

62Moderate · 23% of overall
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
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
37.8/42Issue resolution — 90% of issues closed
26/30PR acceptance — 283/327 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs283
open_issues1
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.9
closed_unmerged_prs44
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
30/30Ownership backing — organization-owned
20/20Verified domain
11.2/25Owner reach — 35 followers of apitally
14.5/25Track record — 12 public repos, account ~3 yr old
Inputs used
followers35
owner_typeOrganization
is_verifiedyes
owner_loginapitally
public_repos12
account_age_days1,166

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://apitally.io
10/10Repository description
10/10Topics — 16 topics
0/10Wiki
Inputs used
topicsapi, monitoring, api-analytics, api-monitoring, api-observability, django-ninja, django-rest-framework, fastapi, flask, python, rest-api, litestar, api-logging, blacksheep, django, starlette
has_wikino
homepagehttps://apitally.io
docs_sitehttps://apitally.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/26 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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 — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.2
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_packages6
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:apitally@0.25.1 runtime dependency closure — what installing the published package pulls in — 6 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.

68Good · 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://docs.apitally.io/llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.apitally.io/llms.txt
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 bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — apitally/py.typed
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 88 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsapitally/py.typed
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0.88
How it's scored
27/45Type-checkable code — Python with type-check config (apitally/py.typed)
55/55Manageable file sizes — 0/52 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes22,492
source_files_sampled52
oversized_source_files0

Key facts

225GitHub stars
1contributors
191commits, last 12 months
0days since last push
69releases
1bus factor
1open 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 ★ / 10 ⇿
0Stars
10Forks
40Releases

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.

02468101022024-102025-092026-07
Major 0Minor 13Patch 27

Each point covers 2 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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 17:33 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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/26 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIbackoff>=2.0.0pyproject.toml
PyPIopentelemetry-sdk>=1.39.1,<2.0.0pyproject.toml
PyPIpsutil>=5.9.6pyproject.toml
PyPItyping-extensions>=4.0.0pyproject.toml
All dependencies 126

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

RegistryPackageVersionRelation
PyPIbackoff2.2.1direct
PyPIopentelemetry-sdk1.44.0direct
PyPIpsutil7.2.2direct
PyPItyping-extensions4.16.0direct
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIanyio4.15.0indirect
PyPIasgiref3.12.1indirect
PyPIasync-timeout5.0.1indirect
PyPIblacksheep2.6.3indirect
PyPIblinker1.9.0indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.1indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.0indirect
PyPIcryptography46.0.7indirect
PyPIdefusedxml0.7.1indirect
PyPIdistlib0.4.3indirect
PyPIdjango5.2.17indirect
PyPIdjango6.1.1indirect
PyPIdjango-ninja1.7.0indirect
PyPIdjango-types0.24.0indirect
PyPIdjangorestframework3.18.0indirect
PyPIdjangorestframework-types0.9.0indirect
PyPIessentials1.1.9indirect
PyPIessentials-openapi1.4.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfaker40.38.0indirect
PyPIfastapi0.141.1indirect
PyPIfilelock3.32.5indirect
PyPIflask3.1.3indirect
PyPIguardpost1.1.0indirect
PyPIh110.16.0indirect
PyPIh24.4.1indirect
PyPIhpack4.2.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttptools0.8.0indirect
PyPIhttpx0.27.2indirect
PyPIhyperframe6.1.0indirect
PyPIidentify2.6.19indirect
PyPIidna3.19indirect
PyPIinflection0.5.1indirect
PyPIiniconfig2.3.0indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPIlitestar2.24.0indirect
PyPIlitestar-htmx0.5.0indirect
PyPIloguru0.7.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImsgspec0.21.1indirect
PyPImultidict6.7.1indirect
PyPImultipart2.0.0indirect
PyPInodeenv1.10.0indirect
PyPIopentelemetry-api1.44.0indirect
PyPIopentelemetry-instrumentation0.65b0indirect
PyPIopentelemetry-instrumentation-asyncpg0.65b0indirect
PyPIopentelemetry-instrumentation-botocore0.65b0indirect
PyPIopentelemetry-instrumentation-dbapi0.65b0indirect
PyPIopentelemetry-instrumentation-httpx0.65b0indirect
PyPIopentelemetry-instrumentation-mysql0.65b0indirect
PyPIopentelemetry-instrumentation-psycopg0.65b0indirect
PyPIopentelemetry-instrumentation-psycopg20.65b0indirect
PyPIopentelemetry-instrumentation-pymongo0.65b0indirect
PyPIopentelemetry-instrumentation-redis0.65b0indirect
PyPIopentelemetry-instrumentation-requests0.65b0indirect
PyPIopentelemetry-instrumentation-sqlalchemy0.65b0indirect
PyPIopentelemetry-propagator-aws-xray1.0.2indirect
PyPIopentelemetry-semantic-conventions0.65b0indirect
PyPIopentelemetry-util-http0.65b0indirect
PyPIpackaging26.3indirect
PyPIplatformdirs4.11.7indirect
PyPIpluggy1.6.0indirect
PyPIpolyfactory3.3.0indirect
PyPIpre-commit4.6.2indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.5indirect
PyPIpydantic-core2.46.5indirect
PyPIpygments2.21.0indirect
PyPIpyjwt2.12.1indirect
PyPIpytest8.4.2indirect
PyPIpytest-asyncio0.21.2indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-httpx0.33.0indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-discovery1.6.0indirect
PyPIpyyaml6.0.3indirect
PyPIrequests2.34.2indirect
PyPIrequests-mock1.12.1indirect
PyPIrich15.0.0indirect
PyPIrich-click1.9.8indirect
PyPIrodi2.0.8indirect
PyPIruff0.15.22indirect
PyPIsentry-sdk2.68.1indirect
PyPIsniffio1.3.1indirect
PyPIsqlparse0.6.0indirect
PyPIstarlette1.6.0indirect
PyPItomli2.4.1indirect
PyPIty0.0.78indirect
PyPItypes-colorama0.4.15.20260508indirect
PyPItypes-docutils0.23.0.20260827indirect
PyPItypes-gevent26.8.0.20260811indirect
PyPItypes-greenlet3.5.0.20260518indirect
PyPItypes-pexpect4.9.0.20260518indirect
PyPItypes-psutil7.2.2.20260827indirect
PyPItypes-psycopg22.9.21.20260724indirect
PyPItypes-pygments2.21.0.20260819indirect
PyPItypes-pysocks1.7.1.20260518indirect
PyPItypes-pyyaml6.0.12.20260815indirect
PyPItypes-requests2.33.0.20260712indirect
PyPItypes-setuptools84.0.0.20260812indirect
PyPItypes-six1.17.0.20260724indirect
PyPItypes-ujson5.10.0.20250822indirect
PyPItyping-inspection0.4.4indirect
PyPItzdata2026.3indirect
PyPIuritemplate4.2.0indirect
PyPIurllib32.7.0indirect
PyPIvirtualenv21.7.8indirect
PyPIwebsockets15.0.1indirect
PyPIwerkzeug3.1.8indirect
PyPIwin32-setctime1.2.0indirect
PyPIwrapt2.4.0indirect
Dependency advisories 0

Installing pypi:apitally@0.25.1 pulls in 6 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.