Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-19 17:03 UTC

bact / licenseid

A Python CLI and library to get the SPDX License ID from license text

PythonApache-2.0★ 1 star⑂ 0 forkssince Apr 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

bact/licenseid holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on Community & Adoption (34/100). It was last updated today. 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

Arthit SuriyawongkulPersonal account
193 followers157 public repossince Sep 2009SPDX AI Working Group

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIlicenseid0.3.65,731130 days agocopyrightlicenselicense-identifierlicense-matcherlicenseidmatcheropensourcespdxspdx-license-id

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
8.3/36Commit cadence12/52 weeks with commits
18/18Commit volume144 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year144
human_commit_share0.97
days_since_last_push0
active_weeks_last_year12
How it's scored
27/27Ships releases13 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~12.5 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count13
latest_release_tagv0.3.6
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases12.5

Community & Adoption

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

34At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io, www.bestpractices.dev
has_pull_request_templateno
How it's scored
50.1/80Monthly downloads5,731 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageslicenseid
dependents
ecosystemspypi
total_downloads
monthly_downloads5,731
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 94% of commits
2.7/13.5Contributor breadth2 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.935
How it's scored
21/42Issue resolution50% of issues closed
27.6/30PR acceptance23/25 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues5
closed_issues5
prs_merged_7d4
prs_decided_7d4
prs_merged_30d7
prs_decided_30d7
issue_closed_ratio0.5
closed_unmerged_prs2
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
16.4/25Owner reach193 followers of bact
25/25Track record157 public repos, account ~16 yr old
Inputs used
followers193
owner_typeUser
is_verified
owner_loginbact
public_repos157
account_age_days6,179
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter config.flake8
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pypi.org/project/licenseid/
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicslicense, license-checking, license-mapping, license-matcher, sbom-tool, spdx-license-identifier, spdx-licenses
has_wikiyes
homepagehttps://pypi.org/project/licenseid/
docs_sitehttps://pypi.org/project/licenseid/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0.5/2.5CII-Best-Practicesbadge detected: InProgress
0/7.5Code-ReviewFound 0/19 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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 3 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.4

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.

67Good · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md, AGENTS.md, CLAUDE.md, GEMINI.md
0/15Machine-readable docs (llms.txt)
17.6/40Legible commit history32 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.33
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md, GEMINI.md
agent_instruction_max_bytes9,625
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.flake8
11/11Static type checkingsrc/licenseid/py.typed
0/10Reproducible environment
10/10Demonstrated agent practice10 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configssrc/licenseid/py.typed
agent_commit_share0.1
toolchain_manifests
dependency_bot_commit_share0.03
How it's scored
27/45Type-checkable codePython with type-check config (src/licenseid/py.typed)
55/55Manageable file sizes0/97 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes39,506
source_files_sampled97
oversized_source_files0

Key facts

1GitHub stars
2contributors
144commits, last 12 months
0days since last push
13releases
1bus factor
5open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:licenseid@0.3.6; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-08-19 17:02 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
2CII-Best-Practicesbadge detected: InProgress
0Code-ReviewFound 0/19 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIbeautifulsoup4>=4.15.0pyproject.toml
PyPIclick>=8.4.2pyproject.toml
PyPIpy-spdx-license>=0.0.1pyproject.toml
PyPIrapidfuzz>=3.14.5pyproject.toml
PyPIrequests>=2.33.0pyproject.toml
PyPItyping_extensions>=4.16.0pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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

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