@snack-uikit/markdown
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@snack-uikit/fields | AI (dependencies): Sibling package from same cloud-ru-tech org with 253 approved packages; consistent publisher track record. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component; empty description is a consistent pattern across the snack-uikit package family. | ai |
Versions (showing 100 of 136)
| Version | Deps | Published |
|---|---|---|
| 0.5.62 | 10 / 0 | |
| 0.5.61 | 10 / 0 | |
| 0.5.60 | 10 / 0 | |
| 0.5.59 | 10 / 0 | |
| 0.5.58 | 10 / 0 | |
| 0.5.57 | 10 / 0 | |
| 0.5.56 | 10 / 0 | |
| 0.5.55 | 10 / 0 | |
| 0.5.54 | 10 / 0 | |
| 0.5.53 | 10 / 0 | |
| 0.5.52 | 10 / 0 | |
| 0.5.51 | 10 / 0 | |
| 0.5.50 | 10 / 0 | |
| 0.5.49 | 10 / 0 | |
| 0.5.48 | 10 / 0 | |
| 0.5.47 | 10 / 0 | |
| 0.5.46 | 10 / 0 | |
| 0.5.45 | 10 / 0 | |
| 0.5.44 | 10 / 0 | |
| 0.5.43 | 10 / 0 | |
| 0.5.42 | 10 / 0 | |
| 0.5.41 | 10 / 0 | |
| 0.5.40 | 10 / 0 | |
| 0.5.39 | 10 / 0 | |
| 0.5.38 | 10 / 0 | |
| 0.5.37 | 10 / 0 | |
| 0.5.36 | 10 / 0 | |
| 0.5.35 | 10 / 0 | |
| 0.5.34 | 10 / 0 | |
| 0.5.33 | 10 / 0 | |
| 0.5.32 | 10 / 0 | |
| 0.5.31 | 10 / 0 | |
| 0.5.30 | 10 / 0 | |
| 0.5.29 | 10 / 0 | |
| 0.5.28 | 10 / 0 | |
| 0.5.27 | 10 / 0 | |
| 0.5.26 | 10 / 0 | |
| 0.5.25 | 10 / 0 | |
| 0.5.24 | 10 / 0 | |
| 0.5.23 | 10 / 0 | |
| 0.5.22 | 10 / 0 | |
| 0.5.21 | 10 / 0 | |
| 0.5.20 | 10 / 0 | |
| 0.5.19 | 10 / 0 | |
| 0.5.18 | 10 / 0 | |
| 0.5.17 | 10 / 0 | |
| 0.5.16 | 10 / 0 | |
| 0.5.15 | 10 / 0 | |
| 0.5.14 | 10 / 0 | |
| 0.5.13 | 10 / 0 | |
| 0.5.12 | 10 / 0 | |
| 0.5.11 | 10 / 0 | |
| 0.5.10 | 10 / 0 | |
| 0.5.9 | 10 / 0 | |
| 0.5.8 | 10 / 0 | |
| 0.5.7 | 10 / 0 | |
| 0.5.6 | 10 / 0 | |
| 0.5.5 | 10 / 0 | |
| 0.5.4 | 10 / 0 | |
| 0.5.3 | 10 / 0 | |
| 0.5.2 | 10 / 0 | |
| 0.5.1 | 10 / 0 | |
| 0.5.0 | 10 / 0 | |
| 0.4.13 | 10 / 0 | |
| 0.4.12 | 10 / 0 | |
| 0.4.11 | 10 / 0 | |
| 0.4.10 | 10 / 0 | |
| 0.4.9 | 10 / 0 | |
| 0.4.8 | 10 / 0 | |
| 0.4.7 | 10 / 0 | |
| 0.4.6 | 10 / 0 | |
| 0.4.5 | 10 / 0 | |
| 0.4.4 | 10 / 0 | |
| 0.4.3 | 10 / 0 | |
| 0.4.2 | 10 / 0 | |
| 0.4.1 | 10 / 0 | |
| 0.4.0 | 10 / 0 | |
| 0.3.55 | 10 / 0 | |
| 0.3.54 | 10 / 0 | |
| 0.3.53 | 10 / 0 | |
| 0.3.52 | 10 / 0 | |
| 0.3.51 | 10 / 0 | |
| 0.3.50 | 10 / 0 | |
| 0.3.49 | 10 / 0 | |
| 0.3.48 | 10 / 0 | |
| 0.3.47 | 10 / 0 | |
| 0.3.46 | 10 / 0 | |
| 0.3.45 | 10 / 0 | |
| 0.3.44 | 10 / 0 | |
| 0.3.43 | 10 / 0 | |
| 0.3.42 | 10 / 0 | |
| 0.3.41 | 10 / 0 | |
| 0.3.40 | 10 / 0 | |
| 0.3.39 | 10 / 0 | |
| 0.3.38 | 10 / 0 | |
| 0.3.37 | 10 / 0 | |
| 0.3.36 | 10 / 0 | |
| 0.3.35 | 10 / 0 | |
| 0.3.34 | 10 / 0 | |
| 0.3.33 | 10 / 0 |
v0.5.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.