@snack-uikit/tree No license 19 versions

@snack-uikit/tree

npm Repository Homepage

19

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

yetiheadagrigoriicloud-ru-tech

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:cancelable-promise	AI (dependencies): cancelable-promise is a legitimate, widely-used utility; no malicious indicators for this package.	ai	2026/06/04
publish-pattern	new-deps-added	AI (publish-pattern): queue-fifo is a well-known benign utility; addition is consistent with tree traversal feature work.	ai	2026/05/30
source-diff	large-new-source-files	AI (source-diff): 75 new files consistent with a new tree component feature; no obfuscation or suspicious patterns flagged.	ai	2026/05/30
publish-pattern	dormant-publish	AI (publish-pattern): Part of a large established monorepo (snack-uikit); dormancy is consistent with component-level release cadence, not takeover.	ai	2026/05/28
dependencies	unvetted-dep:queue-fifo	AI (dependencies): queue-fifo is a well-known, stable FIFO queue utility with no known advisories; legitimate use in a tree component.	ai	2026/05/18
npm-metadata	no-description	AI (npm-metadata): Monorepo UI kit package; empty description is a consistent pattern across all @snack-uikit/* packages.	ai	2026/05/18

Versions (showing 19 of 119)

Version	Deps	Published
0.6.17	10 / 0	2024-08-07
0.6.16	10 / 0	2024-08-07
0.6.15	10 / 0	2024-08-06
0.6.14	10 / 0	2024-07-29
0.6.13	10 / 0	2024-07-19
0.6.12	10 / 0	2024-07-19
0.6.11	10 / 0	2024-06-27
0.6.10	10 / 0	2024-06-26
0.6.9	10 / 0	2024-06-20
0.6.8	10 / 0	2024-06-11
0.6.7	10 / 0	2024-06-11
0.6.6	10 / 0	2024-06-06
0.6.5	10 / 0	2024-05-31
0.6.4	10 / 0	2024-05-30
0.6.3	10 / 0	2024-05-23
0.6.2	10 / 0	2024-05-23
0.6.1	10 / 0	2024-05-13
0.6.0	10 / 0	2024-05-13
0.5.22	10 / 0	2024-05-08

v0.6.17

1 finding

LOW No provenance attestation provenance

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

v0.6.16

1 finding

LOW No provenance attestation provenance

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

v0.6.15

1 finding

LOW No provenance attestation provenance

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

v0.6.14

1 finding

LOW No provenance attestation provenance

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

v0.6.13

1 finding

LOW No provenance attestation provenance

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

v0.6.12

1 finding

LOW No provenance attestation provenance

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

v0.6.11

1 finding

LOW No provenance attestation provenance

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

v0.6.10

1 finding

LOW No provenance attestation provenance

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

v0.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.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.

v0.6.7

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.

v0.6.6

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.

v0.6.5

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.

v0.6.4

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.

v0.6.3

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.

v0.6.2

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.

v0.6.1

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.

v0.6.0

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.

v0.5.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.