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

SigmaHQ / pySigma

Python library to parse and convert Sigma rules into queries (and whatever else you could imagine)

PythonLGPL-2.1★ 601 stars⑂ 160 forkssince Jun 2021View on GitHub ↗

SigmaHQ/pySigma holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Vitality (96/100) and lowest on Security (42/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

34
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 74 is calibrated to 88 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

SigmaOrganization
981 followers31 public repossince Mar 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIpySigma2.0.1385,3061049 days ago

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 2 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 502 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year502
human_commit_share0.97
days_since_last_push2
active_weeks_last_year42

Release discipline

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

69Good · 17% of overall
How it's scored
45.1/60Stars — 601 stars
18.3/25Forks — 160 forks
7.2/15Watchers — 21 watchers
Inputs used
forks160
stars601
watchers21
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (LGPL-2.1)
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_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
74.5/80Monthly downloads — 385,306 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespySigma
dependents—
ecosystemspypi
total_downloads—
monthly_downloads385,306
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?

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.7/22.5Commit distribution — top contributor authored 70% of commits
13.5/13.5Contributor breadth — 68 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled68
top_contributor_share0.704
How it's scored
41.4/42Issue resolution — 99% of issues closed
26.9/30PR acceptance — 343/383 decided PRs merged
8.7/13Newcomer PR acceptance — 4/6 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/15 approved changesets -- score normalized to 1
Inputs used
merged_prs343
open_issues2
closed_issues137
prs_merged_7d0
prs_decided_7d0
prs_merged_30d36
prs_decided_30d40
issue_closed_ratio0.986
closed_unmerged_prs40
first_time_authors_30d6
first_time_prs_merged_30d4
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
21.5/25Owner reach — 981 followers of SigmaHQ
22.2/25Track record — 31 public repos, account ~5 yr old
Inputs used
followers981
owner_typeOrganization
is_verifiedno
owner_loginSigmaHQ
public_repos31
account_age_days2,059

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.black])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

42Weak · 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 — 8 out of 8 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.8/7.5Code-Review — Found 2/15 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 17 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 5 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.3
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier47
security_posture_before_jurisdiction63
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.
How it's scored
26.6/35Direct dependencies free of known advisories — 1 affected: diskcache 5.6.3 (moderate)
10.2/25Indirect dependencies free of known advisories — 1 affected: certifi 2026.10.18 (high 7.4)
37.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 251 days ago
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages16
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages1
Matched the pypi:pySigma@2.0.1 runtime dependency closure — what installing the published package pulls in — 16 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, .github/instructions/docs.md, .github/instructions/sigma.md, .github/instructions/tests.md
0/15Machine-readable docs (llms.txt)
37.9/40Legible commit history — 69 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.711
agent_instruction_files.github/copilot-instructions.md, .github/instructions/docs.md, .github/instructions/sigma.md, .github/instructions/tests.md
agent_instruction_max_bytes3,187
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.black])
11/11Static type checking — mypy.ini, sigma/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 27 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsmypy.ini, sigma/py.typed
agent_commit_share0.27
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (mypy.ini, sigma/py.typed)
53/55Manageable file sizes — 4/108 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes140,470
source_files_sampled108
oversized_source_files4

Key facts

601GitHub stars
68contributors
502commits, last 12 months
2days since last push
100releases
1bus factor
2open 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 ★ / 160 ⇿
0Stars
160Forks
100Releases

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.

0408012016015942021-062024-022026-10
Major 2Minor 13Patch 83

Each point covers 5 days.

OpenSSF Scorecard 6.3 / 10
6.3aggregate

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-21 00:16 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-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/15 approved changesets -- score normalized to 1
10Contributorsproject has 17 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 5 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIpackaging^26.3pyproject.toml
PyPIpyparsing^3.2.5pyproject.toml
PyPIpyyaml^6.0.3pyproject.toml
PyPIrequests^2.32.5pyproject.toml
PyPIjinja2^3.1.6pyproject.toml
PyPItypes-pyyaml^6.0.12.20260815pyproject.toml
PyPIdiskcache^5.6.3pyproject.toml
PyPIdiskcache-stubs>=5.6.3pyproject.toml
PyPIjq^1.12pyproject.toml
PyPIgoogle-re2>=1.0pyproject.toml
All dependencies 64

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

RegistryPackageVersionRelation
PyPIdiskcache5.6.3direct
PyPIdiskcache-stubs5.6.3.6.20240818direct
PyPIgoogle-re21.1.20251105direct
PyPIjinja23.1.6direct
PyPIjq1.12.0direct
PyPIpackaging26.3direct
PyPIpyparsing3.3.3direct
PyPIpyyaml6.0.3direct
PyPIrequests2.34.2direct
PyPItypes-pyyaml6.0.12.20260906direct
PyPIalabaster1.0.0indirect
PyPIast-serialize0.12.1indirect
PyPIastroid4.3.3indirect
PyPIbabel2.18.0indirect
PyPIblack26.5.1indirect
PyPIcertifi2026.7.22indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.2indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.2indirect
PyPIdefusedxml0.7.1indirect
PyPIdill0.4.1indirect
PyPIdistlib0.4.3indirect
PyPIdocutils0.21.2indirect
PyPIfilelock4.0.10indirect
PyPIidentify2.6.20indirect
PyPIidna3.20indirect
PyPIimagesize2.0.1indirect
PyPIiniconfig2.3.0indirect
PyPIisort9.0.2indirect
PyPIlibrt0.16.0indirect
PyPImarkupsafe3.0.4indirect
PyPImccabe0.7.0indirect
PyPImypy2.4.0indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.11.0indirect
PyPIpathspec1.1.1indirect
PyPIpip26.2.1indirect
PyPIplatformdirs4.12.3indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.2indirect
PyPIpygments2.21.0indirect
PyPIpylint4.1.2indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-mypy1.0.1indirect
PyPIpython-discovery1.6.1indirect
PyPIpytokens0.4.1indirect
PyPIroman-numerals4.1.0indirect
PyPIroman-numerals-py4.1.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsphinx8.2.3indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItomlkit0.15.1indirect
PyPItypes-requests2.33.0.20260906indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.8.0indirect
PyPIvirtualenv21.14.5indirect
Dependency advisories 2

Installing pypi:pySigma@2.0.1 pulls in 16 packages, direct and transitive: 2 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2026.10.18indirecthigh22026.10.19
diskcache5.6.3directmoderate2—

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.