Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 22:33 UTC

camptocamp / tag-publish

PythonBSD-2-Clause★ 1 star⑂ 0 forkssince Nov 2024View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

camptocamp/tag-publish holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (81/100) and lowest on Community & Adoption (36/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

69
overall / 100
Good

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.

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

Ownership

CamptocampOrganization
275 followers1,068 public repossince Oct 2008

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPItag-publish1.2.612,4221674 days agoci

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
15.9/36Commit cadence23/52 weeks with commits
18/18Commit volume114 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year114
human_commit_share0.4
days_since_last_push1
active_weeks_last_year23
How it's scored
27/27Ships releases25 releases published
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~60.6 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count25
latest_release_tag1.2.6
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases60.6

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

36Weak · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
2.7/15Watchers4 watchers
Inputs used
forks0
stars1
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-2-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
54.6/80Monthly downloads12,422 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestag-publish
dependents
ecosystemspypi
total_downloads
monthly_downloads12,422
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?

52Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution0% of issues closed
27.8/30PR acceptance200/216 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs200
open_issues2
closed_issues0
prs_merged_7d2
prs_decided_7d2
prs_merged_30d9
prs_decided_30d9
issue_closed_ratio0
closed_unmerged_prs16
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 backingorganization-owned
0/20Verified domain
17.5/25Owner reach275 followers of camptocamp
25/25Track record1,068 public repos, account ~17 yr old
Inputs used
followers275
owner_typeOrganization
is_verifiedno
owner_logincamptocamp
public_repos1,068
account_age_days6,541

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 4 days ago
20/20Version history167 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestag-publish
ecosystemspypi
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests21 out of 21 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

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicsgeospatial
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

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-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests21 out of 21 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
0/7.5Code-ReviewFound 0/10 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging. 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_packages62
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:tag-publish@1.2.6 runtime dependency closure — what installing the published package pulls in — 62 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)
26.7/40Legible commit history20 of 40 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.5
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingtag_publish/py.typed
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance47 of the last 100 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstag_publish/py.typed
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.47
How it's scored
27/45Type-checkable codePython with type-check config (tag_publish/py.typed)
55/55Manageable file sizes0/8 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes20,223
source_files_sampled8
oversized_source_files0

Key facts

1GitHub stars
1contributors
114commits, last 12 months
1days since last push
25releases
1bus factor
2open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

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-05 22:32 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests21 out of 21 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/10 approved changesets -- score normalized to 0
10Contributorsproject has 6 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 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIrequests<3,>=2pyproject.toml
PyPItwine<7,>=6pyproject.toml
PyPIPyYAML<7,>=6pyproject.toml
PyPIid<2,>=1pyproject.toml
PyPIsecurity-md<2,>=1pyproject.toml
PyPIapplications-download<2,>=1pyproject.toml
PyPIjsonschema-validator-new<1,>=0pyproject.toml
PyPIdebian-inspector<32,>=31pyproject.toml
PyPImulti-repo-automation<2,>=1pyproject.toml
PyPIgithubkit<1,>=0pyproject.toml
All dependencies 110

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

RegistryPackageVersionRelation
PyPIapplications-download1.7.0direct
PyPIdebian-inspector31.1.1direct
PyPIgithubkit0.14.3direct
PyPIid1.5.0direct
PyPIjsonschema-validator-new0.3.2direct
PyPImulti-repo-automation1.7.0direct
PyPIpyyaml6.0.3direct
PyPIrequests2.33.0direct
PyPIsecurity-md1.0.0direct
PyPItwine6.2.0direct
PyPIannotated-types0.8.0indirect
PyPIanyio4.14.2indirect
PyPIanysqlite0.0.5indirect
PyPIast-serialize0.8.0indirect
PyPIastroid4.0.4indirect
PyPIattrs26.1.0indirect
PyPIbackports-tarfile1.2.0indirect
PyPIbandit1.9.4indirect
PyPIbuild1.5.0indirect
PyPIc2cciutils1.7.5indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIchardet7.6.0indirect
PyPIcharset-normalizer3.5.1indirect
PyPIcolorama0.4.6indirect
PyPIconfigupdater3.2indirect
PyPIcryptography50.0.0indirect
PyPIdefusedxml0.7.1indirect
PyPIdill0.4.1indirect
PyPIdocutils0.23indirect
PyPIdodgy0.2.1indirect
PyPIexceptiongroup1.3.1indirect
PyPIflake87.3.0indirect
PyPIflake8-polyfill1.0.2indirect
PyPIh110.16.0indirect
PyPIhishel0.1.5indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIidentify2.6.19indirect
PyPIidna3.19indirect
PyPIimportlib-metadata9.0.0indirect
PyPIisort8.0.1indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.1.2indirect
PyPIjaraco-functools4.6.0indirect
PyPIjeepney0.9.0indirect
PyPIjson50.15.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIkeyring25.7.0indirect
PyPIlibrt0.15.0indirect
PyPImarkdown3.10.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkdown-table2020.12.3indirect
PyPImccabe0.7.0indirect
PyPImdurl0.1.2indirect
PyPImore-itertools11.1.0indirect
PyPImsgpack1.2.1indirect
PyPImypy2.3.1indirect
PyPImypy-extensions1.1.0indirect
PyPInh30.3.7indirect
PyPIpackaging26.3indirect
PyPIpathspec1.1.1indirect
PyPIpep8-naming0.10.0indirect
PyPIplatformdirs4.11.4indirect
PyPIpoetry2.4.1indirect
PyPIpoetry-plugin-export1.10.0indirect
PyPIpre-commit4.6.1indirect
PyPIprospector1.19.1indirect
PyPIprospector-profile-duplicated1.12.0indirect
PyPIprospector-profile-utils1.27.0indirect
PyPIpycodestyle2.14.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.46.4indirect
PyPIpydocstyle6.3.0indirect
PyPIpyflakes3.4.0indirect
PyPIpygments2.21.0indirect
PyPIpylint4.0.7indirect
PyPIpylint-celery0.3indirect
PyPIpylint-django2.8.0indirect
PyPIpylint-plugin-utils0.9.0indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpyroma5.0.1indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIreadme-renderer45.0indirect
PyPIreferencing0.37.0indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrequirements-detector1.6.0indirect
PyPIrfc39862.0.0indirect
PyPIrich15.0.0indirect
PyPIrpds-py0.30.0indirect
PyPIruamel-yaml0.19.1indirect
PyPIruff0.15.21indirect
PyPIsecretstorage3.5.0indirect
PyPIsemver3.0.4indirect
PyPIsetoptconf-tmp0.3.1indirect
PyPIsetuptools84.0.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIstevedore5.8.0indirect
PyPItoml0.10.2indirect
PyPItomli2.4.1indirect
PyPItomlkit0.15.1indirect
PyPItrove-classifiers2026.6.1.19indirect
PyPItypes-pyyaml6.0.12.20260724indirect
PyPItypes-requests2.33.0.20260712indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib32.7.0indirect
PyPIzipp4.1.0indirect
Dependency advisories 0

Installing pypi:tag-publish@1.2.6 pulls in 62 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 statisticsPyPI.