← Home

@wix/atlas

npm
24
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-sessionsegozi_wixbryanp-wixmaksymawixethanpwix-org-headlessfalconciroir-wix

Keywords

wixSdkBackendModulewixSdkPageModulewixSdkPublicModule

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK package; templated name, no description, and no repo URL are expected patterns for this publisher's SDK suite. ai
npm-metadata no-description AI (npm-metadata): Auto-generated Wix SDK packages consistently lack descriptions; not a malware indicator here. ai
provenance no-provenance AI (provenance): Wix CI publisher pattern does not include Sigstore provenance; consistent across all 38 versions. ai

Versions (showing 24 of 24)

Version Deps Published
1.0.41 3 / 2
1.0.40 3 / 2
1.0.39 3 / 2
1.0.38 3 / 2
1.0.37 3 / 2
1.0.36 3 / 2
1.0.35 3 / 2
1.0.34 3 / 2
1.0.33 3 / 2
1.0.32 3 / 2
1.0.31 3 / 2
1.0.30 3 / 2
1.0.29 3 / 2
1.0.28 3 / 2
1.0.27 3 / 2
1.0.26 3 / 2
1.0.25 3 / 2
1.0.24 3 / 2
1.0.23 3 / 1
1.0.22 3 / 1
1.0.21 3 / 1
1.0.20 3 / 1
1.0.19 3 / 4
1.0.18 3 / 4

v1.0.41

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

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

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

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

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

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.