@coding-flow/flow-design
flow-engine design components
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@flowgram.ai/export-plugin | AI (dependencies): Legitimate ByteDance/Flowgram SDK dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/form-materials | AI (dependencies): Legitimate ByteDance/Flowgram SDK dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/minimap-plugin | AI (dependencies): Legitimate ByteDance/Flowgram SDK dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/fixed-layout-editor | AI (dependencies): Legitimate ByteDance/Flowgram SDK dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/fixed-semi-materials | AI (dependencies): Legitimate ByteDance/Flowgram SDK dependency; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/panel-manager-plugin | AI (dependencies): Legitimate ByteDance/Flowgram SDK dependency; stable across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.0.46 | 21 / 4 | |
| 0.0.45 | 21 / 4 | |
| 0.0.44 | 21 / 4 | |
| 0.0.43 | 21 / 4 | |
| 0.0.42 | 21 / 4 | |
| 0.0.41 | 21 / 4 | |
| 0.0.40 | 26 / 4 | |
| 0.0.38 | 26 / 4 | |
| 0.0.37 | 26 / 4 | |
| 0.0.35 | 26 / 4 | |
| 0.0.34 | 26 / 4 | |
| 0.0.33 | 26 / 4 | |
| 0.0.32 | 26 / 4 | |
| 0.0.31 | 26 / 4 | |
| 0.0.30 | 26 / 4 | |
| 0.0.29 | 26 / 4 | |
| 0.0.26 | 26 / 4 | |
| 0.0.22 | 26 / 4 | |
| 0.0.21 | 26 / 4 | |
| 0.0.20 | 26 / 4 | |
| 0.0.19 | 26 / 4 | |
| 0.0.18 | 26 / 4 | |
| 0.0.17 | 26 / 4 | |
| 0.0.16 | 26 / 4 | |
| 0.0.15 | 26 / 4 | |
| 0.0.13 | 26 / 4 | |
| 0.0.12 | 26 / 4 | |
| 0.0.11 | 26 / 4 | |
| 0.0.10 | 26 / 4 | |
| 0.0.9 | 26 / 4 | |
| 0.0.8 | 26 / 4 | |
| 0.0.7 | 26 / 4 | |
| 0.0.6 | 26 / 4 | |
| 0.0.5 | 26 / 4 | |
| 0.0.4 | 26 / 4 | |
| 0.0.3 | 26 / 4 | |
| 0.0.2 | 26 / 4 | |
| 0.0.1 | 26 / 4 |
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.