@flowgram.ai/form-materials
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Organizational package from ByteDance; missing description is benign given repo context. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is sparse; not a disqualifier for established org packages. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/editor | AI (dependencies): First-party sibling package in the bytedance/flowgram.ai monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/coze-editor | AI (dependencies): First-party sibling package in the bytedance/flowgram.ai monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@flowgram.ai/json-schema | AI (dependencies): First-party sibling package in the bytedance/flowgram.ai monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@douyinfe/semi-ui | AI (dependencies): Well-known ByteDance Semi Design UI library; not a risk for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 11 / 16 | |
| 1.0.8 | 11 / 16 | |
| 1.0.7 | 11 / 16 | |
| 1.0.6 | 11 / 16 | |
| 1.0.3 | 11 / 16 | |
| 1.0.2 | 11 / 16 | |
| 1.0.1 | 11 / 16 |
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.