motion-dom
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): motion-dom is a legitimate high-traffic sub-package of the Motion library ecosystem published by the trusted popmotion account. Metadata gaps and inflated semver reflect monorepo extraction patterns, not spam/malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 34M+ weekly downloads; missing description is a metadata hygiene issue, not a security signal. | ai | |
| source-diff | obfuscated-file:dist/size-rollup-motion-value.js | AI (source-diff): Minified rollup bundle for size measurement, listed in bundlesize config. Standard animation library code, no suspicious patterns. | ai | |
| source-diff | obfuscated-file:dist/size-rollup-style-effect.js | AI (source-diff): Minified rollup bundle for size measurement, listed in bundlesize config. Standard animation library code, no suspicious patterns. | ai | |
| source-diff | obfuscated-file:dist/index.d.ts | AI (source-diff): TypeScript declaration file with long SVG attribute type definitions. Not obfuscated, just extensive type unions. | ai |
Versions (showing 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 11.16.3 | 1 / 0 | |
| 11.16.1 | 1 / 0 | |
| 11.16.0 | 1 / 0 | |
| 11.14.3 | 0 / 0 | |
| 11.14.1 | 0 / 0 | |
| 11.14.0 | 0 / 0 | |
| 11.13.0 | 0 / 0 |
v11.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.