← Home

@chainsafe/ssz

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

wemeetagainmatthewkeil

Keywords

ethereumserenitysimple serializessz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Published with SLSA provenance via GitHub Actions; gitHead absence reflects CI change, not compromise. ai
publish-pattern dormant-publish AI (publish-pattern): Established ChainSafe org package with SLSA provenance; dormancy is normal maintenance cadence. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @chainsafe/ssz from ChainSafe Systems; levenshtein match to 'qs' is a false positive with no credible impersonation intent. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() used solely to create a dynamically named class extending a superclass — a standard JS pattern for runtime class naming in schema/serialization libraries. ai

Versions (showing 7 of 7)

Version Deps Published
1.6.0 2 / 5
1.5.0 2 / 5
1.4.0 2 / 5
1.3.4 2 / 5
1.3.0 2 / 4
1.2.2 2 / 4
1.2.1 2 / 4

v1.6.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v1.5.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.