motion
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
Keywords
Versions (showing 69 of 169)
| Version | Deps | Published |
|---|---|---|
| 12.16.0 | 2 / 0 | |
| 12.15.0 | 2 / 0 | |
| 12.14.0 | 2 / 0 | |
| 12.13.0 | 2 / 0 | |
| 12.12.2 | 2 / 0 | |
| 12.12.1 | 2 / 0 | |
| 12.12.0 | 2 / 0 | |
| 12.11.4 | 2 / 0 | |
| 12.11.3 | 2 / 0 | |
| 12.11.2 | 2 / 0 | |
| 12.11.1 | 2 / 0 | |
| 12.11.0 | 2 / 0 | |
| 12.10.6 | 2 / 0 | |
| 12.10.5 | 2 / 0 | |
| 12.10.4 | 2 / 0 | |
| 12.10.3 | 2 / 0 | |
| 12.10.2 | 2 / 0 | |
| 12.10.1 | 2 / 0 | |
| 12.10.0 | 2 / 0 | |
| 12.9.7 | 2 / 0 | |
| 12.9.6 | 2 / 0 | |
| 12.9.5 | 2 / 0 | |
| 12.9.4 | 2 / 0 | |
| 12.9.3 | 2 / 0 | |
| 12.9.2 | 2 / 0 | |
| 12.9.1 | 2 / 0 | |
| 12.9.0 | 2 / 0 | |
| 12.8.2 | 2 / 0 | |
| 12.8.0 | 2 / 0 | |
| 12.7.5 | 2 / 0 | |
| 12.7.4 | 2 / 0 | |
| 12.7.3 | 2 / 0 | |
| 12.7.2 | 2 / 0 | |
| 12.7.1 | 2 / 0 | |
| 12.7.0 | 2 / 0 | |
| 12.6.5 | 2 / 0 | |
| 12.6.4 | 2 / 0 | |
| 12.6.3 | 2 / 0 | |
| 12.6.2 | 2 / 0 | |
| 12.6.1 | 2 / 0 | |
| 12.6.0 | 2 / 0 | |
| 12.5.0 | 2 / 0 | |
| 12.4.13 | 2 / 0 | |
| 12.4.12 | 2 / 0 | |
| 12.4.11 | 2 / 0 | |
| 12.4.10 | 2 / 0 | |
| 12.4.9 | 2 / 0 | |
| 12.4.7 | 2 / 0 | |
| 12.4.6 | 2 / 0 | |
| 12.4.5 | 2 / 0 | |
| 12.4.4 | 2 / 0 | |
| 12.4.3 | 2 / 0 | |
| 12.4.2 | 2 / 0 | |
| 12.4.1 | 2 / 0 | |
| 12.4.0 | 2 / 0 | |
| 12.3.1 | 2 / 0 | |
| 12.3.0 | 2 / 0 | |
| 12.2.0 | 2 / 0 | |
| 12.1.0 | 2 / 0 | |
| 12.0.11 | 2 / 0 | |
| 12.0.10 | 2 / 0 | |
| 12.0.9 | 2 / 0 | |
| 12.0.8 | 2 / 0 | |
| 12.0.6 | 2 / 0 | |
| 12.0.5 | 2 / 0 | |
| 12.0.4 | 2 / 0 | |
| 12.0.3 | 2 / 0 | |
| 12.0.1 | 2 / 0 | |
| 12.0.0 | 2 / 0 |
v12.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.