Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 01:59 UTC

pulseengine / sigil

Sigil — Supply chain security for WebAssembly. Embedded signatures, Sigstore keyless signing, SLSA provenance. Part of the PulseEngine toolchain.

RustNo license detected★ 0 stars⑂ 0 forkssince Nov 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

pulseengine/sigil holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (12/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

pulseengineOrganization
15 followers49 public repossince May 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iowsc-clipoints to another repo — not scored0.11.0251226 days agomodulessignatureswebassemblycryptographywasm
crates.iowscpoints to another repo — not scored0.11.04281326 days agomodulessignatureswebassemblycryptographywasm
crates.iowsc-dssepoints to another repo — not scored0.11.012136 days agoattestationdsseno-stdsignaturescryptography
crates.iowsc-attestationpoints to another repo — not scored0.11.02,3131736 days agoattestationprovenancesupply-chainwebassemblydevelopment-toolswasm
crates.iowsc-verify-corepoints to another repo — not scored0.11.0400226 days agomodulessignatureswebassemblywasmno-stdcryptography

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
23.5/36Commit cadence — 34/52 weeks with commits
18/18Commit volume — 308 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year308
human_commit_share0.33
days_since_last_push2
active_weeks_last_year34

Release discipline

96Exceptional
How it's scored
27/27Ships releases — 21 releases published
36/36Release recency — latest release 36 days ago
27/27Release cadence — a release every ~11.3 days
6/10OpenSSF Scorecard: Signed-Releases — 4 out of the last 5 releases have a total of 4 signed artifacts.
Inputs used
releases_count21
latest_release_tagv0.11.0
releases_from_tagsno
days_since_latest_release36
mean_days_between_releases11.3

Community & Adoption

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

12Critical · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno

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
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.2/22.5Commit distribution — top contributor authored 46% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.456
How it's scored
27.1/42Issue resolution — 65% of issues closed
28.7/30PR acceptance — 196/205 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs196
open_issues23
closed_issues42
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.646
closed_unmerged_prs9
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
8.7/25Owner reach — 15 followers of pulseengine
15/25Track record — 49 public repos, account ~1 yr old
Inputs used
followers15
owner_typeOrganization
is_verifiedno
owner_loginpulseengine
public_repos49
account_age_days481

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 13 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicspulseengine, rust, sigstore, slsa, supply-chain-security, webassembly
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?

59Moderate · 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 — 30 out of 30 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/7.5Code-Review — Found 0/7 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
4.5/7.5Signed-Releases — 4 out of the last 5 releases have a total of 4 signed artifacts.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
3/7.5Vulnerabilities — 6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

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.

85Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 33 of 33 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes16,793
How it's scored
12.6/18One-command bootstrap — Cargo.toml, examples/wasmtime-loader/Cargo.toml, fuzz/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — Dockerfile, Nix, lockfile
10/10Demonstrated agent practice — 27 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 67 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixyes
has_testsyes
lockfilesCargo.lock
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.27
toolchain_manifestsCargo.toml, examples/wasmtime-loader/Cargo.toml, fuzz/Cargo.toml, src/attestation/Cargo.toml, src/cli/Cargo.toml, src/component/Cargo.toml, src/crypto/Cargo.toml, src/dsse/Cargo.toml, src/lib/Cargo.toml, src/verify-core/Cargo.toml, verification/torture-runner/Cargo.toml, verification/witness-harness/Cargo.toml
dependency_bot_commit_share0.67
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.1/55Manageable file sizes — 4/117 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes169,332
source_files_sampled117
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
5contributors
308commits, last 12 months
2days since last push
21releases
2bus factor
23open issues
crates.iopackage ecosystems

Data collection warnings

  • crates package 'wsc-cli' points at a different repository (https://github.com/pulseengine/wsc); excluded from ecosystem scoring
  • crates package 'wsc' points at a different repository (https://github.com/pulseengine/wsc); excluded from ecosystem scoring
  • crates package 'wsc-dsse' points at a different repository (https://github.com/pulseengine/wsc); excluded from ecosystem scoring
  • Could not fetch crates package 'wsc-crypto' from its registry
  • Could not fetch crates package 'wsc-component' from its registry
  • crates package 'wsc-attestation' points at a different repository (https://github.com/pulseengine/wsc); excluded from ecosystem scoring
  • crates package 'wsc-verify-core' points at a different repository (https://github.com/pulseengine/wsc); excluded from ecosystem scoring
  • Could not fetch crates package 'wsc-torture-runner' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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-17 01:59 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-Tests30 out of 30 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/7 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
6Signed-Releases4 out of the last 5 releases have a total of 4 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 78
RegistryPackageVersion constraintManifest
crates.ioserde1.0src/attestation/Cargo.toml
crates.ioserde_json1.0src/attestation/Cargo.toml
crates.iochrono0.4src/attestation/Cargo.toml
crates.iohex0.4src/attestation/Cargo.toml
crates.iogetrandom0.3src/attestation/Cargo.toml
crates.iosha20.10src/attestation/Cargo.toml
crates.iobase640.22src/attestation/Cargo.toml
crates.ioed25519-compact2.1src/attestation/Cargo.toml
crates.ioct-codecs1.1src/attestation/Cargo.toml
crates.ioin_toto_attestation0.1src/attestation/Cargo.toml
crates.ioclap4.5.50src/cli/Cargo.toml
crates.ioenv_logger0.11.8src/cli/Cargo.toml
crates.ioregex1.12.2src/cli/Cargo.toml
crates.ioureq3.1.2src/cli/Cargo.toml
crates.iowasi0.14.7src/cli/Cargo.toml
crates.iowsc0.11.0src/cli/Cargo.toml
crates.ioserde_json1.0src/cli/Cargo.toml
crates.iowsc0.11.0src/component/Cargo.toml
crates.iowit-bindgen0.60.0src/component/Cargo.toml
crates.iowsc0.11.0src/crypto/Cargo.toml
crates.iowit-bindgen0.47.0src/crypto/Cargo.toml
crates.ioed25519-compact2.1src/crypto/Cargo.toml
crates.ioserde1.0src/dsse/Cargo.toml
crates.ioserde_json1.0src/dsse/Cargo.toml
crates.iobase640.22src/dsse/Cargo.toml
crates.ioed25519-compact2.3src/dsse/Cargo.toml
crates.iowsc-verify-core0.11.0src/lib/Cargo.toml
crates.iowsc-attestation0.11.0src/lib/Cargo.toml
crates.iowsc-dsse0.11.0src/lib/Cargo.toml
crates.ioanyhow1.0.100src/lib/Cargo.toml
crates.ioct-codecs1.1.6src/lib/Cargo.toml
crates.ioed25519-compact2.1.1src/lib/Cargo.toml
crates.iogetrandom0.3.4src/lib/Cargo.toml
crates.iohmac-sha2561.1.12src/lib/Cargo.toml
crates.iolog0.4.28src/lib/Cargo.toml
crates.iotracing0.1src/lib/Cargo.toml
crates.iotracing-subscriber0.3src/lib/Cargo.toml
crates.iosha20.10src/lib/Cargo.toml
crates.ioregex1.12.2src/lib/Cargo.toml
crates.iothiserror2.0.17src/lib/Cargo.toml
crates.iozeroize1.8src/lib/Cargo.toml
crates.iowasi0.14.7src/lib/Cargo.toml
crates.ioserde1.0src/lib/Cargo.toml
crates.ioserde_json1.0src/lib/Cargo.toml
crates.ioserde_jcs0.2src/lib/Cargo.toml
crates.iobase640.22src/lib/Cargo.toml
crates.iox509-parser0.16src/lib/Cargo.toml
crates.iotime0.3src/lib/Cargo.toml
crates.iochrono0.4src/lib/Cargo.toml
crates.iohex0.4src/lib/Cargo.toml
crates.iouuid1.11src/lib/Cargo.toml
crates.ioureq3.1.2src/lib/Cargo.toml
crates.iospki0.7src/lib/Cargo.toml
crates.iop2560.13src/lib/Cargo.toml
crates.ioecdsa0.16src/lib/Cargo.toml
crates.iorustls-webpki0.103src/lib/Cargo.toml
crates.iorustls-pki-types1.11src/lib/Cargo.toml
crates.iorustls0.23src/lib/Cargo.toml
crates.iowebpki-roots1.0src/lib/Cargo.toml
crates.iopem4.0src/lib/Cargo.toml
crates.ioconst-oid0.10src/lib/Cargo.toml
crates.iorcgen0.13src/lib/Cargo.toml
crates.iotoml1.1src/lib/Cargo.toml
crates.iomaybe-async0.2src/lib/Cargo.toml
crates.iokeyring3src/lib/Cargo.toml
crates.iotokio1.43src/lib/Cargo.toml
crates.ioreqwest0.12src/lib/Cargo.toml
crates.ioregorus0.10src/lib/Cargo.toml
crates.iowasmtime47src/lib/Cargo.toml
crates.ioct-codecs1.1.6src/verify-core/Cargo.toml
crates.ioed25519-compact2.1.1src/verify-core/Cargo.toml
crates.iogetrandom0.3.4src/verify-core/Cargo.toml
crates.iohmac-sha2561.1.12src/verify-core/Cargo.toml
crates.iolog0.4.28src/verify-core/Cargo.toml
crates.iothiserror2.0.17src/verify-core/Cargo.toml
crates.iozeroize1.8src/verify-core/Cargo.toml
crates.iowsc-verify-core—verification/torture-runner/Cargo.toml
crates.iowsc-verify-core—verification/witness-harness/Cargo.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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io.