← Home

velocity-animate

Accelerated JavaScript animation.

71
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

julianshapirokviranirycochet

Keywords

velocityanimationjqueryanimateuivelocity.jsvelocityjsjavascript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change to rycochet occurred in 2018; rycochet is listed as co-author and has 71 approved packages over ~8 years. Legitimate maintainer transition. ai
maintainer-change maintainer-added AI (maintainer-change): rycochet is a listed co-author of velocity-animate with a long clean track record; legitimate maintainer addition. ai

Versions (showing 71 of 71)

Version Deps Published
2.0.6 0 / 22
2.0.5 0 / 20
2.0.4 0 / 20
2.0.3 0 / 19
2.0.2 0 / 9
2.0.1 0 / 9
1.5.2 0 / 3
1.5.1 0 / 3
1.5.0 0 / 3
1.4.3 0 / 3
1.4.2 0 / 3
1.4.0 0 / 3
1.3.2 0 / 3
1.3.1 0 / 3
1.3.0 0 / 3
1.2.3 1 / 6
1.2.2 1 / 6
1.2.1 1 / 6
1.2.0 1 / 6
1.1.0 1 / 6
1.0.1 1 / 6
1.0.0 1 / 6
0.11.9 1 / 6
0.11.8 1 / 6
0.11.7 1 / 6
0.11.6 1 / 6
0.11.5 1 / 6
0.11.4 1 / 6
0.11.3 1 / 6
0.11.2 1 / 6
0.11.1 1 / 6
0.11.0 1 / 6
0.10.1 1 / 6
0.10.0 1 / 6
0.9.0 1 / 6
0.8.0 1 / 6
0.7.0 1 / 6
0.6.0 1 / 6
0.5.3 1 / 6
0.5.2 1 / 6
0.5.1 1 / 6
0.5.0 1 / 6
0.4.1 1 / 6
0.4.0 1 / 6
0.3.0 1 / 6
0.2.1 1 / 6
0.2.0 1 / 6
0.1.0 1 / 6
0.0.55 1 / 0
0.0.54 1 / 0
0.0.53 1 / 0
0.0.52 1 / 0
0.0.51 1 / 0
0.0.23 1 / 6
0.0.22 1 / 6
0.0.21 1 / 6
0.0.20 1 / 6
0.0.19 1 / 6
0.0.18 1 / 6
0.0.17 1 / 6
0.0.16 1 / 6
0.0.15 1 / 6
0.0.14 1 / 6
0.0.13 1 / 6
0.0.12 1 / 6
0.0.11 1 / 6
0.0.10 1 / 6
0.0.9 1 / 6
0.0.5 1 / 0
0.0.4 1 / 0
0.0.3 1 / 0

v2.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

2 findings
HIGH Publisher changed: kvirani → rycochet (on 2018-02-11) provenance

This version was published by a different npm account than previous versions on 2018-02-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: thekenwheeler → kvirani (on 2016-10-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-20. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julianshapiro → thekenwheeler (on 2015-09-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-09-26. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.