← Home

@stacksjs/ts-validation

npm Repository Homepage
37
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

chrisbreuerglenn123

Keywords

typescriptstarterkitbunpackage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:dompurify AI (phantom-deps): dompurify is a declared runtime dependency; phantom-dep false positive for this package. ai
install-scripts install-script:postinstall FP sweep: benign dev-tooling install script (git-hooks/husky/patch-package/build/codegen etc.), verified from tarball; not malware. Flip disposition to accept. sean

Versions (showing 37 of 37)

Version Deps Published
0.5.2 0 / 1
0.5.1 0 / 1
0.5.0 1 / 1
0.4.10 1 / 2
0.4.9 1 / 2
0.4.8 1 / 3
0.4.7 1 / 11
0.4.6 1 / 11
0.4.5 1 / 10
0.4.4 1 / 10
0.4.3 1 / 10
0.4.2 1 / 10
0.4.1 1 / 10
0.4.0 1 / 10
0.3.7 1 / 10
0.3.6 1 / 10
0.3.5 1 / 10
0.3.4 1 / 10
0.3.3 1 / 10
0.3.2 1 / 10
0.3.1 1 / 10
0.3.0 1 / 10
0.2.9 1 / 10
0.2.8 1 / 10
0.2.7 1 / 10
0.2.6 1 / 10
0.2.5 1 / 10
0.2.4 1 / 10
0.2.3 1 / 10
0.2.2 1 / 10
0.2.1 1 / 10
0.2.0 1 / 10
0.1.9 1 / 10
0.1.8 1 / 10
0.1.4 1 / 10
0.1.1 1 / 10
0.1.0 1 / 10

v0.5.2

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

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

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

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

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