@reactflow/core
Core components and util functions of React Flow.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @reactflow/core is the legitimate core module of the React Flow library under the @reactflow npm scope; 'core' suffix is a standard monorepo convention, not a typosquat of 'cors'. | ai | |
| source-diff | obfuscated-file:dist/esm/index.mjs | AI (source-diff): dist/esm/index.mjs is a standard Rollup-produced ESM build artifact for this React library. Minified lines are expected; code is readable and non-malicious. | ai | |
| phantom-deps | phantom-dep:@types/d3 | AI (phantom-deps): @types/d3 is a TypeScript type package listed as a dependency for type resolution; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/d3-drag | AI (phantom-deps): @types/d3-drag is a TypeScript type package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/d3-zoom | AI (phantom-deps): @types/d3-zoom is a TypeScript type package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/d3-selection | AI (phantom-deps): @types/d3-selection is a TypeScript type package; not directly imported at runtime by design. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 11.11.4 | 9 / 8 | |
| 11.11.3 | 9 / 8 | |
| 11.11.2 | 9 / 8 | |
| 11.11.1 | 9 / 8 | |
| 11.11.0 | 9 / 8 | |
| 11.10.4 | 9 / 8 | |
| 11.10.3 | 9 / 8 | |
| 11.10.2 | 9 / 8 | |
| 11.10.1 | 9 / 8 | |
| 11.10.0 | 9 / 8 | |
| 11.9.4 | 9 / 8 | |
| 11.9.3 | 9 / 8 | |
| 11.9.2 | 9 / 8 | |
| 11.9.1 | 9 / 8 | |
| 11.9.0 | 9 / 8 | |
| 11.8.3 | 9 / 8 | |
| 11.8.2 | 9 / 8 | |
| 11.8.1 | 9 / 8 | |
| 11.8.0 | 9 / 8 | |
| 11.7.4 | 9 / 8 | |
| 11.7.3 | 9 / 8 | |
| 11.7.2 | 9 / 8 | |
| 11.7.1 | 9 / 8 | |
| 11.7.0 | 9 / 8 | |
| 11.6.1 | 9 / 8 | |
| 11.6.0 | 9 / 8 | |
| 11.5.5 | 9 / 8 | |
| 11.5.4 | 9 / 8 | |
| 11.5.3 | 9 / 8 | |
| 11.5.2 | 9 / 8 | |
| 11.5.1 | 9 / 8 | |
| 11.5.0 | 9 / 8 | |
| 11.4.2 | 9 / 8 | |
| 11.4.1 | 9 / 8 | |
| 11.4.0 | 9 / 8 | |
| 11.3.2 | 9 / 8 | |
| 11.3.1 | 9 / 8 | |
| 11.3.0 | 9 / 8 | |
| 11.2.0 | 9 / 8 | |
| 11.1.2 | 9 / 7 | |
| 11.1.1 | 9 / 7 | |
| 11.1.0 | 9 / 7 | |
| 11.0.0 | 9 / 7 |
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
2 findingsNewly 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.
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.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.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
2 findingsPackage name '@reactflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.