← Home

@scayle/storefront-product-detail

npm

Collection of essential composables and utilities to work with product detail

27
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

hector_gonzalez_ayay-henribecklouisa_schmidt_ayconnor-pearson-aymarcel-domke-aykyosifovscayle-automationcloud-panel-ay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SCAYLE org package with 34 published versions; missing gitHead reflects CI change, not a supply chain risk. ai

Versions (showing 27 of 27)

Version Deps Published
1.9.0 0 / 23
1.8.0 0 / 24
1.7.0 0 / 24
1.6.3 0 / 24
1.6.2 0 / 24
1.6.1 0 / 24
1.6.0 0 / 24
1.5.6 0 / 24
1.5.5 0 / 24
1.5.4 0 / 24
1.5.3 0 / 24
1.5.2 0 / 24
1.5.1 0 / 23
1.5.0 0 / 24
1.4.2 0 / 23
1.4.1 0 / 23
1.4.0 0 / 23
1.3.0 0 / 23
1.2.0 0 / 23
1.1.4 0 / 22
1.1.3 0 / 22
1.1.2 0 / 19
1.1.1 0 / 19
1.1.0 0 / 19
1.0.2 0 / 19
1.0.1 0 / 19
1.0.0 0 / 19

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

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

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