Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 02:10 UTC

fosslight / fosslight_source_scanner

FOSSLight Source Scanner

PythonApache-2.0★ 32 stars⑂ 11 forkssince Apr 2021View on GitHub ↗
KindCommand-line toolPluginLibraryhow this is determined

fosslight/fosslight_source_scanner holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (96/100) and lowest on Security (21/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

FOSSLightOrganization
40 followers24 public repossince Apr 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIfosslight_source2.3.163,3761180 days agofosslightscannerlicensesource

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.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 217 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year217
human_commit_share0.83
days_since_last_push0
active_weeks_last_year43

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 ~9.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.3.16
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases9.1

Community & Adoption

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

52Moderate · 17% of overall
How it's scored
24.2/60Stars — 32 stars
8.3/25Forks — 11 forks
3.3/15Watchers — 5 watchers
Inputs used
forks11
stars32
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
47/80Monthly downloads — 3,376 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfosslight_source
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,376
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.8/22.5Commit distribution — top contributor authored 43% of commits
13.5/13.5Contributor breadth — 14 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled14
top_contributor_share0.433
How it's scored
35/42Issue resolution — 83% of issues closed
26.4/30PR acceptance — 269/306 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs269
open_issues3
closed_issues15
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.833
closed_unmerged_prs37
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
0/20Verified domain
11.6/25Owner reach — 40 followers of fosslight
21.2/25Track record — 24 public repos, account ~5 yr old
Inputs used
followers40
owner_typeOrganization
is_verifiedno
owner_loginfosslight
public_repos24
account_age_days2,018

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

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 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
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
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 site — https://pypi.org/project/fosslight-source
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://pypi.org/project/fosslight-source
docs_sitehttps://pypi.org/project/fosslight-source
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements-dev.txt
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages19
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 2 resolved dependencies against OSV. 19 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.

46Weak · 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 83 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.94
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — tox.ini
0/11Static type checking
10/10Reproducible environment — Dockerfile
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 — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
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/31 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes35,850
source_files_sampled31
oversized_source_files0

Key facts

32GitHub stars
14contributors
217commits, last 12 months
0days since last push
100releases
2bus factor
3open 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:fosslight_source@2.3.16; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
53Releases

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.

0246810121122021-062023-042025-03
Major 1Minor 2Patch 50

Each point covers 4 days.

Direct dependencies 18
RegistryPackageVersion constraintManifest
PyPIsetuptools<=80.10.2pyproject.toml
PyPIpyparsing—pyproject.toml
PyPIscanoss>=1.45.0pyproject.toml
PyPIXlsxWriter—pyproject.toml
PyPIfosslight_util>=2.2.14pyproject.toml
PyPIPyYAML—pyproject.toml
PyPIwheel>=0.38.1pyproject.toml
PyPIintbitset—pyproject.toml
PyPIscancode-toolkit>=32.5.0pyproject.toml
PyPIlxml>=6.0.1pyproject.toml
PyPIcryptography<49pyproject.toml
PyPIfingerprints==1.2.3pyproject.toml
PyPInormality==2.6.1pyproject.toml
PyPIpsycopg2-binary>=2.9.10pyproject.toml
PyPItomli—pyproject.toml
PyPItqdm—pyproject.toml
PyPItruststore—pyproject.toml
PyPIpluggy<1.7.0pyproject.toml
All dependencies 21

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

RegistryPackageVersionRelation
PyPIcryptography—direct
PyPIfingerprints1.2.3direct
PyPIfosslight-util—direct
PyPIintbitset—direct
PyPIlxml—direct
PyPInormality2.6.1direct
PyPIpluggy—direct
PyPIpsycopg2-binary—direct
PyPIpyparsing—direct
PyPIpyyaml—direct
PyPIscancode-toolkit—direct
PyPIscanoss—direct
PyPIsetuptools—direct
PyPItomli—direct
PyPItqdm—direct
PyPItruststore—direct
PyPIwheel—direct
PyPIxlsxwriter—direct
PyPIflake8—indirect
PyPIpytest—indirect
PyPItox—indirect
Dependency advisories 0

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

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.