reactflow
A highly customizable React library for building node-based editors and interactive flow charts
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transfer from enome to wbkd (webkid GmbH), the known maintainers of React Flow. Well-documented OSS project transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): webk1d is the official npm account for the wbkd/React Flow team; legitimate maintainer addition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): enome transferred the package name to the React Flow team; removal is expected. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from enome to webk1d reflects the known, legitimate project transfer to wbkd. | ai | |
| source-diff | obfuscated-file:dist/umd/index.js | AI (source-diff): Standard Rollup-generated UMD bundle with minification; not obfuscation. Normal for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from legacy stub to full v11 release is expected and legitimate. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 11.11.4 | 6 / 7 | |
| 11.11.3 | 6 / 7 | |
| 11.11.2 | 6 / 7 | |
| 11.11.1 | 6 / 7 | |
| 11.11.0 | 6 / 7 | |
| 11.10.4 | 6 / 7 | |
| 11.10.3 | 6 / 7 | |
| 11.10.2 | 6 / 7 | |
| 11.10.1 | 6 / 7 | |
| 11.10.0 | 6 / 7 | |
| 11.9.4 | 6 / 7 | |
| 11.9.3 | 6 / 7 | |
| 11.9.2 | 6 / 7 | |
| 11.9.1 | 6 / 7 | |
| 11.9.0 | 6 / 7 | |
| 11.8.3 | 6 / 7 | |
| 11.8.2 | 6 / 7 | |
| 11.8.1 | 6 / 7 | |
| 11.8.0 | 6 / 7 | |
| 11.7.4 | 6 / 7 | |
| 11.7.3 | 6 / 7 | |
| 11.7.2 | 6 / 7 | |
| 11.7.1 | 6 / 7 | |
| 11.7.0 | 6 / 7 | |
| 11.6.1 | 5 / 7 | |
| 11.6.0 | 5 / 7 | |
| 11.5.6 | 5 / 7 | |
| 11.5.5 | 5 / 7 | |
| 11.5.4 | 5 / 7 | |
| 11.5.3 | 5 / 7 | |
| 11.5.2 | 5 / 7 | |
| 11.5.1 | 5 / 7 | |
| 11.5.0 | 5 / 7 | |
| 11.4.2 | 5 / 7 | |
| 11.4.1 | 5 / 7 | |
| 11.4.0 | 5 / 7 | |
| 11.3.3 | 5 / 7 | |
| 11.3.2 | 5 / 7 | |
| 11.3.1 | 5 / 7 | |
| 11.3.0 | 5 / 7 | |
| 11.2.0 | 4 / 7 | |
| 11.1.2 | 4 / 7 | |
| 11.1.1 | 4 / 7 | |
| 11.1.0 | 4 / 7 | |
| 11.0.0 | 4 / 7 | |
| 0.1.0 | 7 / 0 |
v11.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
4 findingsAll previous maintainers (enome) were replaced by new maintainers (webk1d). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2022-09-28. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.