← Home

@wix/auto_sdk_loyalty_tiers

51
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

yoavwix-cishahatawixnpmwix-ambassadorwix-ci-publisherwix-bi-publishergalil-teamusability-sessionsyurynixydanivmayacoamitde007haimbrum-wixyoungshinobiethanpshlomitc-wixarielhwix-org-headlessfalconcinadavlacroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): wix-ci-publisher is Wix's established CI publisher account with 773 approved packages; transition from individual wix accounts is expected. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal aligns with Wix centralizing publishing under wix-ci-publisher; not indicative of takeover. ai
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK package; templated naming, no description/repo are expected for this publisher's pipeline. ai
npm-metadata no-description AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; stable false positive for this package family. ai
provenance no-provenance AI (provenance): Wix CI pipeline does not attach Sigstore provenance; consistent across all approved versions. ai

Versions (showing 51 of 51)

Version Deps Published
1.0.51 3 / 2
1.0.50 3 / 2
1.0.49 2 / 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.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 / 1
1.0.16 2 / 1
1.0.15 2 / 1
1.0.14 2 / 1
1.0.13 2 / 2
1.0.12 2 / 2
1.0.11 2 / 2
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 / 1
1.0.3 2 / 1
1.0.2 2 / 1
1.0.1 2 / 1
1.0.0 2 / 1

v1.0.9

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

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

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

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

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

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.