← Home

@snack-uikit/info-block

npm Repository Homepage
20
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

yetiheadagrigoriicloud-ru-tech

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@snack-uikit/utils AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. ai
dependencies unvetted-dep:@snack-uikit/button AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. ai
dependencies unvetted-dep:@snack-uikit/tooltip AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. ai
dependencies unvetted-dep:@snack-uikit/typography AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. ai
dependencies unvetted-dep:@snack-uikit/icon-predefined AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. ai

Versions (showing 20 of 20)

Version Deps Published
0.6.41 6 / 0
0.6.40 6 / 0
0.6.39 6 / 0
0.6.38 6 / 0
0.6.37 6 / 0
0.6.36 6 / 0
0.6.35 6 / 0
0.6.34 6 / 0
0.6.33 6 / 0
0.6.32 6 / 0
0.6.31 6 / 0
0.6.30 6 / 0
0.6.29 6 / 0
0.6.28 6 / 0
0.6.27 6 / 0
0.6.26 6 / 0
0.6.25 6 / 0
0.6.24 6 / 0
0.6.23 6 / 0
0.6.22 6 / 0

v0.6.41

1 finding
LOW No provenance attestation provenance

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

v0.6.33

1 finding
LOW No provenance attestation provenance

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

v0.6.32

1 finding
LOW No provenance attestation provenance

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

v0.6.31

1 finding
LOW No provenance attestation provenance

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

v0.6.30

1 finding
LOW No provenance attestation provenance

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

v0.6.29

1 finding
LOW No provenance attestation provenance

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

v0.6.28

1 finding
LOW No provenance attestation provenance

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

v0.6.27

1 finding
LOW No provenance attestation provenance

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

v0.6.26

1 finding
LOW No provenance attestation provenance

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

v0.6.25

1 finding
LOW No provenance attestation provenance

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

v0.6.24

1 finding
LOW No provenance attestation provenance

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

v0.6.23

1 finding
LOW No provenance attestation provenance

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

v0.6.22

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.