← Home

@remix-run/data-schema

npm Repository Homepage

Tiny, standards-aligned schema validation

4
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

mjackson

Keywords

validationschemastandard-schemavalidatorremix

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Intentional placeholder from official Remix team; 0.0.0 is a namespace reservation, not a malicious pattern here. ai
bogus-package bogus-package AI (bogus-package): Explicitly documented placeholder from a highly trusted publisher; tiny payload and no deps are expected. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.0 1 / 4
0.2.0 1 / 2
0.1.0 1 / 2
0.0.0 0 / 0

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

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

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

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