@wix/atlas
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.