← Home

@wix/auto_sdk_ecom_tax-calculation

52
Versions
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

wix-ciwixnpmwix-ambassadorwix-ci-publisherwix-bi-publisherusability-sessionsbryanp-wixethanpwix-org-headlessfalconciroir-wix

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Wix migrated to wix-ci-publisher CI account; consistent pattern across Wix SDK packages. ai
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK package; templated name/no-description/no-repo are expected patterns across this entire package family. ai
npm-metadata no-description AI (npm-metadata): Stable false positive for Wix auto-generated SDK packages; no description is intentional. ai
provenance no-provenance AI (provenance): Wix CI publisher consistently publishes without Sigstore provenance; stable across all versions. ai

Versions (showing 52 of 52)

Version Deps Published
1.0.51 3 / 2
1.0.50 3 / 2
1.0.49 3 / 2
1.0.48 2 / 2
1.0.47 2 / 2
1.0.46 2 / 2
1.0.45 2 / 2
1.0.44 2 / 2
1.0.43 2 / 2
1.0.42 2 / 2
1.0.41 2 / 2
1.0.40 2 / 2
1.0.39 2 / 2
1.0.38 2 / 2
1.0.37 2 / 2
1.0.36 2 / 2
1.0.35 2 / 2
1.0.34 2 / 2
1.0.33 2 / 2
1.0.32 2 / 2
1.0.31 2 / 2
1.0.30 2 / 2
1.0.29 2 / 2
1.0.28 2 / 2
1.0.27 2 / 2
1.0.26 2 / 2
1.0.25 2 / 2
1.0.24 2 / 2
1.0.23 2 / 2
1.0.22 2 / 2
1.0.21 2 / 2
1.0.20 2 / 2
1.0.19 2 / 2
1.0.18 2 / 2
1.0.17 2 / 2
1.0.16 2 / 2
1.0.15 2 / 2
1.0.14 2 / 2
1.0.13 2 / 2
1.0.12 2 / 2
1.0.11 2 / 1
1.0.10 2 / 1
1.0.9 2 / 1
1.0.8 2 / 1
1.0.7 2 / 1
1.0.6 2 / 1
1.0.5 2 / 1
1.0.4 2 / 2
1.0.3 2 / 1
1.0.2 2 / 1
1.0.1 2 / 1
1.0.0 2 / 1

v1.0.51

1 finding
INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.