← Home

react-motion

npm Repository Homepage

A spring that solves your animation problems.

26
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

chenglounkbt

Keywords

reactcomponentreact-componenttransitiongroupspringtweenmotionanimationtransitionui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:bower_components/react/JSXTransformer.js AI (source-diff): Vendored Facebook JSXTransformer v0.13.3 browserify bundle; standard for 2015-era bower packages. ai
source-diff net-exec-file:bower_components/react/JSXTransformer.js AI (source-diff): JSXTransformer's exec() uses eval to run transformed JSX — documented behavior, not malware. ai
source-diff source-size-tripled AI (source-diff): Size increase from vendored bower_components (React builds); expected for this package era. ai
semgrep semgrep:eval-usage AI (semgrep): eval in JSXTransformer.exec() is the documented API for running transformed JSX code. ai
provenance no-provenance AI (provenance): Package predates Sigstore; no provenance expected for 2015-era publishes. ai
provenance publisher-changed AI (provenance): nkbt is explicitly listed as co-author in package.json alongside chenglou; long-standing npm account (3946 days) with 7 approved packages. Transition in 2017 is a documented co-maintainer handoff. ai

Versions (showing 26 of 26)

Version Deps Published
0.5.2 3 / 33
0.5.1 3 / 33
0.5.0 3 / 33
0.4.8 4 / 34
0.4.7 2 / 34
0.4.6 2 / 34
0.4.5 2 / 34
0.4.4 2 / 30
0.4.3 2 / 30
0.4.2 2 / 30
0.4.1 2 / 30
0.4.0 2 / 30
0.3.1 2 / 30
0.3.0 2 / 25
0.2.7 3 / 24
0.2.6 3 / 24
0.2.5 3 / 24
0.2.4 3 / 21
0.2.3 3 / 21
0.2.2 3 / 21
0.2.1 3 / 21
0.2.0 3 / 15
0.1.0 0 / 14
0.0.3 1 / 6
0.0.2 1 / 6
0.0.1 1 / 6

v0.5.2

2 findings
HIGH Publisher changed: chenglou → nkbt (on 2017-10-02) provenance

This version was published by a different npm account than previous versions on 2017-10-02. 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.

v0.5.1

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: nkbt → chenglou (on 2017-08-28) provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.8

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: chenglou → nkbt (on 2017-04-18) provenance

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

v0.4.7

1 finding
LOW No provenance attestation provenance

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

v0.4.6

1 finding
LOW No provenance attestation provenance

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

v0.4.5

1 finding
INFO No provenance attestation provenance

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

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
INFO No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
INFO No provenance attestation provenance

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

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

3 findings
HIGH New obfuscated file: bower_components/react/JSXTransformer.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: bower_components/react/JSXTransformer.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
INFO No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.