← Home

@conform-to/yup

npm Repository Homepage

Conform helpers for integrating with yup

45
Versions
MIT
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

edmundhung

Keywords

constraint-validationformform-validationhtmlprogressive-enhancementvalidationyup

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Added dep is first-party monorepo sibling package, not third-party. ai
provenance missing-githead AI (provenance): Benign publish-environment artifact from trusted maintainer with clean history. ai
provenance publisher-changed AI (provenance): Package now publishes via GitHub Actions CI with SLSA attestation; this is the expected automated publishing pattern for this repo. ai
dependencies unvetted-dep:@conform-to/dom AI (dependencies): Same-monorepo sibling package; stable false positive for all @conform-to/* packages. ai

Versions (showing 45 of 45)

Version Deps Published
1.20.0 1 / 8
1.19.4 1 / 8
1.19.3 1 / 8
1.19.2 1 / 8
1.19.1 1 / 8
1.19.0 1 / 8
1.18.0 1 / 8
1.17.1 1 / 8
1.17.0 1 / 8
1.16.0 1 / 8
1.15.1 1 / 8
1.15.0 1 / 8
1.14.1 1 / 8
1.14.0 1 / 8
1.13.3 1 / 8
1.13.2 1 / 8
1.13.1 1 / 8
1.13.0 1 / 8
1.12.1 1 / 8
1.12.0 1 / 8
1.11.0 1 / 8
1.10.1 1 / 8
1.10.0 1 / 8
1.9.1 1 / 8
1.9.0 1 / 8
1.8.2 1 / 8
1.8.1 1 / 8
1.8.0 1 / 8
1.7.2 1 / 8
1.7.1 1 / 8
1.7.0 1 / 8
1.6.1 1 / 8
1.6.0 1 / 8
1.5.1 1 / 8
1.5.0 1 / 8
1.4.0 1 / 8
1.3.0 1 / 8
1.2.2 1 / 8
1.2.1 1 / 8
1.2.0 1 / 8
1.1.5 1 / 8
1.1.4 1 / 8
1.1.3 0 / 8
1.1.2 0 / 1
1.1.1 0 / 1

v1.20.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.4.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: edmundhung.

LOW No provenance attestation provenance

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

v1.3.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: edmundhung.

LOW No provenance attestation provenance

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

v1.2.2

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: edmundhung.

LOW No provenance attestation provenance

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

v1.2.1

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: edmundhung.

LOW No provenance attestation provenance

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

v1.2.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: edmundhung.

LOW No provenance attestation provenance

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

v1.1.5

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: edmundhung.

LOW No provenance attestation provenance

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

v1.1.4

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: edmundhung.

LOW No provenance attestation provenance

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

v1.1.3

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.

v1.1.2

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.

v1.1.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.