@vue-flow/core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:d3-selection | AI (phantom-deps): Used internally for drag/zoom; likely missed by static import scan due to bundling. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @vue-flow/core is a legitimate Vue diagram library; Levenshtein match against 'cors' is a false positive. | ai | |
| phantom-deps | phantom-dep:d3-interpolate | AI (phantom-deps): d3-interpolate is a legitimate runtime dep used in bundled output; phantom-dep heuristic misfires on bundled packages. | ai |
Versions (showing 100 of 178)
| Version | Deps | Published |
|---|---|---|
| 1.48.2 | 5 / 15 | |
| 1.48.1 | 5 / 15 | |
| 1.48.0 | 5 / 15 | |
| 1.47.0 | 5 / 15 | |
| 1.46.5 | 5 / 15 | |
| 1.46.4 | 5 / 15 | |
| 1.46.3 | 5 / 15 | |
| 1.46.2 | 5 / 15 | |
| 1.46.1 | 5 / 15 | |
| 1.46.0 | 5 / 15 | |
| 1.45.1 | 5 / 15 | |
| 1.45.0 | 5 / 15 | |
| 1.44.0 | 5 / 15 | |
| 1.43.2 | 4 / 13 | |
| 1.43.1 | 4 / 13 | |
| 1.43.0 | 4 / 13 | |
| 1.42.5 | 4 / 13 | |
| 1.42.4 | 4 / 13 | |
| 1.42.3 | 4 / 13 | |
| 1.42.2 | 4 / 13 | |
| 1.42.1 | 4 / 13 | |
| 1.42.0 | 4 / 13 | |
| 1.41.7 | 4 / 13 | |
| 1.41.6 | 4 / 13 | |
| 1.41.5 | 4 / 13 | |
| 1.41.4 | 4 / 13 | |
| 1.41.3 | 4 / 13 | |
| 1.41.2 | 4 / 13 | |
| 1.41.1 | 4 / 13 | |
| 1.41.0 | 4 / 13 | |
| 1.40.1 | 4 / 13 | |
| 1.40.0 | 4 / 13 | |
| 1.39.3 | 4 / 13 | |
| 1.39.2 | 4 / 13 | |
| 1.39.1 | 4 / 13 | |
| 1.39.0 | 4 / 13 | |
| 1.38.5 | 4 / 13 | |
| 1.38.4 | 4 / 13 | |
| 1.38.3 | 4 / 13 | |
| 1.38.2 | 4 / 13 | |
| 1.38.1 | 4 / 13 | |
| 1.38.0 | 4 / 13 | |
| 1.37.1 | 4 / 13 | |
| 1.37.0 | 4 / 13 | |
| 1.36.0 | 4 / 13 | |
| 1.35.0 | 4 / 13 | |
| 1.34.1 | 4 / 13 | |
| 1.34.0 | 4 / 13 | |
| 1.33.8 | 4 / 13 | |
| 1.33.7 | 4 / 13 | |
| 1.33.6 | 4 / 13 | |
| 1.33.5 | 4 / 13 | |
| 1.33.4 | 4 / 13 | |
| 1.33.3 | 4 / 13 | |
| 1.33.2 | 4 / 13 | |
| 1.33.1 | 4 / 13 | |
| 1.33.0 | 4 / 13 | |
| 1.32.1 | 4 / 13 | |
| 1.32.0 | 4 / 13 | |
| 1.31.0 | 4 / 13 | |
| 1.30.1 | 4 / 13 | |
| 1.30.0 | 4 / 13 | |
| 1.29.2 | 4 / 13 | |
| 1.29.1 | 4 / 13 | |
| 1.29.0 | 4 / 13 | |
| 1.28.0 | 4 / 13 | |
| 1.27.1 | 4 / 13 | |
| 1.27.0 | 4 / 15 | |
| 1.26.0 | 4 / 15 | |
| 1.25.3 | 4 / 15 | |
| 1.25.2 | 4 / 15 | |
| 1.25.1 | 4 / 15 | |
| 1.25.0 | 4 / 15 | |
| 1.24.2 | 4 / 15 | |
| 1.24.1 | 4 / 15 | |
| 1.24.0 | 4 / 15 | |
| 1.23.0 | 4 / 15 | |
| 1.22.3 | 4 / 15 | |
| 1.22.2 | 4 / 15 | |
| 1.22.1 | 4 / 15 | |
| 1.22.0 | 4 / 15 | |
| 1.21.3 | 4 / 15 | |
| 1.21.2 | 4 / 15 | |
| 1.21.1 | 4 / 15 | |
| 1.21.0 | 4 / 15 | |
| 1.20.2 | 4 / 15 | |
| 1.20.1 | 4 / 15 | |
| 1.20.0 | 4 / 16 | |
| 1.19.4 | 4 / 16 | |
| 1.19.3 | 4 / 16 | |
| 1.19.2 | 4 / 16 | |
| 1.19.1 | 4 / 16 | |
| 1.19.0 | 4 / 16 | |
| 1.18.2 | 4 / 16 | |
| 1.18.1 | 4 / 16 | |
| 1.18.0 | 4 / 16 | |
| 1.17.6 | 4 / 16 | |
| 1.17.5 | 4 / 16 | |
| 1.17.4 | 4 / 16 | |
| 1.17.3 | 4 / 16 |
v1.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.