@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 77)
| 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 | |
| 1.68.0 | 11 / 12 | |
| 1.67.0 | 11 / 12 | |
| 1.66.0 | 11 / 12 | |
| 1.65.0 | 11 / 12 | |
| 1.64.0 | 11 / 12 | |
| 1.63.0 | 11 / 12 | |
| 1.62.0 | 11 / 12 | |
| 1.61.0 | 11 / 12 | |
| 1.60.0 | 11 / 12 | |
| 1.59.0 | 11 / 12 | |
| 1.58.0 | 11 / 12 | |
| 1.57.0 | 11 / 12 | |
| 1.56.0 | 11 / 12 | |
| 1.55.0 | 11 / 12 | |
| 1.54.0 | 11 / 12 | |
| 1.53.0 | 11 / 12 | |
| 1.52.0 | 11 / 12 | |
| 1.51.0 | 11 / 12 | |
| 1.50.0 | 11 / 12 | |
| 1.49.0 | 11 / 12 | |
| 1.48.0 | 11 / 12 | |
| 1.47.0 | 11 / 12 | |
| 1.46.0 | 11 / 12 | |
| 1.45.0 | 11 / 12 | |
| 1.44.0 | 11 / 12 | |
| 1.43.0 | 11 / 12 | |
| 1.42.0 | 11 / 12 | |
| 1.41.0 | 11 / 12 | |
| 1.40.0 | 11 / 12 | |
| 1.39.0 | 11 / 12 | |
| 1.38.0 | 11 / 12 | |
| 1.37.0 | 11 / 12 | |
| 1.36.0 | 11 / 12 | |
| 1.35.0 | 11 / 12 | |
| 1.34.0 | 11 / 12 | |
| 1.33.0 | 11 / 12 | |
| 1.32.0 | 11 / 12 | |
| 1.31.0 | 11 / 12 | |
| 1.30.0 | 11 / 12 |
v1.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.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.48.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.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.