@motionone/easing
A collection of easing functions.
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): tslib is a known TypeScript runtime helper; implicit usage via compiled output is standard. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Missing repo/keywords/README detail is typical for scoped monorepo sub-packages; not indicative of spam. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 10.18.0 | 2 / 0 | |
| 10.17.1 | 2 / 0 | |
| 10.17.0 | 2 / 0 | |
| 10.16.3 | 2 / 0 | |
| 10.15.1 | 2 / 0 | |
| 10.15.0 | 2 / 0 | |
| 10.14.0 | 2 / 0 | |
| 10.13.2 | 2 / 0 | |
| 10.13.1 | 2 / 0 | |
| 10.13.0 | 2 / 0 | |
| 10.12.0 | 2 / 0 | |
| 10.9.0 | 2 / 0 | |
| 10.8.2 | 2 / 0 | |
| 10.8.0 | 2 / 0 | |
| 10.7.0 | 2 / 0 | |
| 10.6.2 | 2 / 0 | |
| 10.6.1 | 2 / 0 | |
| 10.6.0 | 2 / 0 |
v10.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.1
2 findingsThis version was published by a different npm account (popmotion) than the most recent previously approved version (motionone) on 2022-02-06. It has since remained available on npm for 1630 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.