Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-14 18:36 UTC

viur-framework / viur-core

The core component of ViUR, the Python framework for modern web development.

PythonMIT★ 16 stars⑂ 15 forkssince Dec 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

viur-framework/viur-core holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on AI Readiness (52/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

ViUROrganization · verified domain
24 followers46 public repossince Mar 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIviur-core3.9.32,7662290 days agoviurframeworkbackend

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 235 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year235
human_commit_share1
days_since_last_push0
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~6.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv3.9.3
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases6.9
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?

52Moderate · 17% of overall
How it's scored
19.1/60Stars — 16 stars
9.6/25Forks — 15 forks
4.3/15Watchers — 7 watchers
Inputs used
forks15
stars16
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
45.9/80Monthly downloads — 2,766 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesviur-core
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,766
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.4/22.5Commit distribution — top contributor authored 50% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled18
top_contributor_share0.495
How it's scored
26.3/42Issue resolution — 63% of issues closed
27/30PR acceptance — 1,267/1,409 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 17/30 approved changesets -- score normalized to 5
Inputs used
merged_prs1,267
open_issues134
closed_issues225
prs_merged_7d1
prs_decided_7d1
prs_merged_30d10
prs_decided_30d10
issue_closed_ratio0.627
closed_unmerged_prs142
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
10.1/25Owner reach — 24 followers of viur-framework
24.2/25Track record — 46 public repos, account ~9 yr old
Inputs used
followers24
owner_typeOrganization
is_verifiedyes
owner_loginviur-framework
public_repos46
account_age_days3,487

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 — 229 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesviur-core
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 17 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_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.viur.dev
10/10Repository description
10/10Topics — 11 topics
0/10Wiki
Inputs used
topicsviur, google-appengine, python3, appengine-python, python-framework, framework, jinja2, python, google-cloud-platform, google-datastore, application-framework
has_wikino
homepagehttps://www.viur.dev
docs_sitehttps://www.viur.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 17 out of 17 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
3.8/7.5Code-Review — Found 17/30 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 12 contributing companies or organizations
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 20 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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 — 17 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
19.6/35Direct dependencies free of known advisories — 1 affected: requests 2.32.4 (moderate 5.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
35.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 203 days ago
Inputs used
sourceosv
advisories34
affected_packages6
assessed_packages37
unassessed_packages28
affected_by_severitycritical 1, high 2, moderate 2, low 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 37 resolved dependencies against OSV. 28 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.2/40Legible commit history — 66 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.66
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
0/11Static type checking
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
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
lockfilesPipfile.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
54/55Manageable file sizes — 3/165 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes82,444
source_files_sampled165
oversized_source_files3

Key facts

16GitHub stars
18contributors
235commits, last 12 months
0days since last push
100releases
2bus factor
134open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:viur-core@3.9.3; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
85Releases

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.

03581013151522019-122023-032026-06
Major 0Minor 3Patch 82

Each point covers 6 days.

OpenSSF Scorecard 5.6 / 10
5.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-10-14 18:35 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
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
5Code-ReviewFound 17/30 approved changesets -- score normalized to 5
10Contributorsproject has 12 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 20 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
0Vulnerabilities17 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
PyPIappengine-python-standard~=2.0pyproject.toml
PyPIDeprecated~=1.2pyproject.toml
PyPIgoogle-api-core~=2.0pyproject.toml
PyPIgoogle-auth~=2.0pyproject.toml
PyPIgoogle-cloud-bigquery~=3.0pyproject.toml
PyPIgoogle-cloud-datastore~=2.0pyproject.toml
PyPIgoogle-cloud-iam~=2.0pyproject.toml
PyPIgoogle-cloud-logging~=3.0pyproject.toml
PyPIgoogle-cloud-recaptcha-enterprise~=1.0pyproject.toml
PyPIgoogle-cloud-secret-manager~=2.0pyproject.toml
PyPIgoogle-cloud-storage>=2,<4pyproject.toml
PyPIgoogle-cloud-tasks~=2.0pyproject.toml
PyPIgoogle-resumable-media~=2.0pyproject.toml
PyPIgoogleapis-common-protos~=1.0pyproject.toml
PyPIgunicorn>=23,<27pyproject.toml
PyPIjinja2~=3.0pyproject.toml
PyPIjsonschema~=4.0pyproject.toml
PyPIlogics-py==0.0.12pyproject.toml
PyPIpillow>=11,<13pyproject.toml
PyPIpyotp~=2.0pyproject.toml
PyPIpytz>=2023pyproject.toml
PyPIpyyaml~=6.0pyproject.toml
PyPIqrcode>=7,<9pyproject.toml
PyPIrequests~=2.0pyproject.toml
PyPItzlocal~=5.0pyproject.toml
PyPIuser-agents~=2.0pyproject.toml
PyPIwebob~=1.0pyproject.toml
All dependencies 65

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

RegistryPackageVersionRelation
PyPIappengine-python-standard—direct
PyPIdeprecated—direct
PyPIgoogle-api-core—direct
PyPIgoogle-auth—direct
PyPIgoogle-cloud-bigquery—direct
PyPIgoogle-cloud-datastore—direct
PyPIgoogle-cloud-iam—direct
PyPIgoogle-cloud-logging—direct
PyPIgoogle-cloud-recaptcha-enterprise—direct
PyPIgoogle-cloud-secret-manager—direct
PyPIgoogle-cloud-storage—direct
PyPIgoogle-cloud-tasks—direct
PyPIgoogle-resumable-media—direct
PyPIgoogleapis-common-protos—direct
PyPIgunicorn—direct
PyPIjinja2—direct
PyPIjinja23.1.6direct
PyPIjsonschema—direct
PyPIlogics-py0.0.12direct
PyPIpillow—direct
PyPIpyotp—direct
PyPIpytz—direct
PyPIpyyaml—direct
PyPIpyyaml6.0.2direct
PyPIqrcode—direct
PyPIrequests—direct
PyPIrequests2.32.4direct
PyPItzlocal—direct
PyPIuser-agents—direct
PyPIwebob—direct
PyPIalabaster1.0.0indirect
PyPIanyio4.9.0indirect
PyPIastroid3.3.11indirect
PyPIbabel2.17.0indirect
PyPIcertifi2025.7.14indirect
PyPIcharset-normalizer3.4.2indirect
PyPIclick8.2.1indirect
PyPIcolorama0.4.6indirect
PyPIdocutils0.21.2indirect
PyPIh110.16.0indirect
PyPIidna3.10indirect
PyPIimagesize1.4.1indirect
PyPImailjet-rest—indirect
PyPImarkupsafe3.0.2indirect
PyPIpackaging25.0indirect
PyPIpygments2.19.2indirect
PyPIroman-numerals-py3.1.0indirect
PyPIsetuptools—indirect
PyPIsniffio1.3.1indirect
PyPIsnowballstemmer3.0.1indirect
PyPIsphinx8.2.3indirect
PyPIsphinx-autoapi3.6.0indirect
PyPIsphinx-autobuild2024.10.3indirect
PyPIsphinx-autodoc-typehints3.2.0indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPIstarlette0.47.2indirect
PyPIurllib32.5.0indirect
PyPIuvicorn0.35.0indirect
PyPIwatchfiles1.1.0indirect
PyPIwebsockets15.0.1indirect
Dependency advisories 6

This repository publishes no package the index resolves, so its own dependency graph was assessed — 37 packages, which also include development and test pins that never ship: 6 carry known advisories, of which 1 are direct. 28 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
anyio4.9.0indirectcritical44.14.2
starlette0.47.2indirecthigh121.3.1
urllib32.5.0indirecthigh122.8.0
requests2.32.4directmoderate22.33.0
idna3.10indirectmoderate23.15
pygments2.19.2indirectlow22.20.0

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.