@wix/motion-edm-autogen-transformations
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Implicit dependency of @babel/runtime; stable across versions. | ai | |
| phantom-deps | phantom-dep:deep-for-each | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@rushstack/eslint-patch | AI (phantom-deps): Config-referenced dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@wix/motion-edm-autogen-common | AI (phantom-deps): Same-org internal dependency; stable for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Wix package; missing description is consistent across the org's tooling packages. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher pattern; provenance not used across this org's packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix tooling package; mass-produced naming, no repo/description are expected for org-internal packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.80.0 | 11 / 13 | |
| 1.79.0 | 11 / 13 | |
| 1.78.0 | 11 / 12 | |
| 1.77.0 | 11 / 12 | |
| 1.76.0 | 11 / 12 | |
| 1.75.0 | 11 / 12 | |
| 1.74.0 | 11 / 12 | |
| 1.73.0 | 11 / 12 | |
| 1.72.0 | 11 / 12 | |
| 1.71.0 | 11 / 12 | |
| 1.70.0 | 11 / 12 | |
| 1.69.0 | 11 / 12 |
v1.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.79.0
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.78.0
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.77.0
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.76.0
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.75.0
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.74.0
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.73.0
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.72.0
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.71.0
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.70.0
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.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.