← Home

@thirstie/ecomm-vue

npm
20
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

thirstie_barttechnology-thirstie

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ramda AI (phantom-deps): Transitive dependency via @thirstie/thirstieclient; stable false positive. ai
phantom-deps phantom-dep:@vueuse/core AI (phantom-deps): Transitive dependency via @thirstie/thirstieclient; stable false positive. ai
phantom-deps phantom-dep:@thirstie/assets AI (phantom-deps): Internal org dependency used transitively; stable false positive. ai
phantom-deps phantom-dep:@thirstie/thirstieclient AI (phantom-deps): Internal org dependency used transitively; stable false positive. ai

Versions (showing 20 of 20)

Version Deps Published
1.5.17 4 / 0
1.5.16 4 / 0
1.5.15 4 / 0
1.5.14 4 / 0
1.5.13 4 / 0
1.5.12 4 / 0
1.5.11 4 / 0
1.5.10 4 / 0
1.5.9 4 / 0
1.5.8 4 / 0
1.5.7 4 / 0
1.5.6 4 / 0
1.5.5 4 / 0
1.5.4 4 / 0
1.5.3 4 / 0
1.5.2 4 / 0
1.5.1 4 / 0
1.5.0 4 / 0
1.4.3 4 / 0
1.4.2 4 / 0

v1.5.11

1 finding
LOW No provenance attestation provenance

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

v1.5.10

1 finding
LOW No provenance attestation provenance

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

v1.5.9

1 finding
LOW No provenance attestation provenance

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

v1.5.8

1 finding
LOW No provenance attestation provenance

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

v1.5.7

1 finding
LOW No provenance attestation provenance

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

v1.5.6

1 finding
LOW No provenance attestation provenance

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

v1.5.5

1 finding
LOW No provenance attestation provenance

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

v1.5.4

1 finding
LOW No provenance attestation provenance

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

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

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