← Home

zod-from-json-schema

npm Repository Homepage
16
Versions
—
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

mark.probst

Keywords

zodjson-schemavalidationtypescriptschema

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from personal account to GitHub Actions CI/CD with SLSA provenance; legitimate automation. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by zod v4 release prompting a compatibility update; established package. ai

Versions (showing 16 of 16)

Version Deps Published
0.5.6 1 / 5
0.5.5 1 / 5
0.5.4 1 / 5
0.5.3 1 / 5
0.5.2 1 / 5
0.5.1 1 / 5
0.5.0 1 / 5
0.4.2 1 / 4
0.4.1 1 / 4
0.4.0 1 / 4
0.1.0 1 / 5
0.0.5 1 / 5
0.0.4 1 / 5
0.0.3 1 / 4
0.0.2 1 / 4
0.0.1 1 / 4

v0.5.6

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.

v0.5.5

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.

v0.5.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.

v0.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

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.