← Home

@flowgram.ai/fixed-semi-materials

6
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

xiamidaxiachenjiawei.iniziobytednpm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@douyinfe/semi-ui AI (dependencies): @douyinfe/semi-ui is ByteDance's established Semi Design UI library; stable dependency for this package. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package; missing description is a consistent pattern across all @flowgram.ai/* packages. ai
provenance no-provenance AI (provenance): No provenance across the entire @flowgram.ai/* monorepo; consistent pattern, not a targeted omission. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.11 5 / 13
1.0.10 5 / 13
1.0.9 5 / 13
1.0.8 5 / 13
1.0.7 5 / 13
1.0.3 5 / 13

v1.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.