@checkstack/ui
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): Internal scoped UI library; missing description is cosmetic and stable across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @radix-ui/react-slider is a legitimate Radix UI primitive; consistent with existing deps pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped UI library; missing metadata is expected for private/internal packages. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a standard Proxy trap for Monaco editor API guarding; not obfuscation. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared runtime dep; phantom-dep heuristic false positive for this React UI library. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; Levenshtein match to uuid is coincidental. | ai | |
| phantom-deps | phantom-dep:recharts | AI (phantom-deps): recharts is declared in dependencies and likely used indirectly or via re-export; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; Levenshtein match to pg is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; Levenshtein match to qs is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; Levenshtein match to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; Levenshtein match to yup is coincidental. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.13.1 | 36 / 22 | |
| 1.13.0 | 36 / 22 | |
| 1.12.0 | 31 / 22 | |
| 1.10.0 | 23 / 22 | |
| 1.9.0 | 23 / 22 | |
| 1.8.3 | 23 / 19 | |
| 1.8.2 | 23 / 19 | |
| 1.8.1 | 23 / 19 | |
| 1.7.0 | 23 / 7 | |
| 1.6.1 | 23 / 7 | |
| 1.6.0 | 23 / 7 | |
| 1.5.0 | 22 / 7 | |
| 1.3.5 | 21 / 6 | |
| 1.3.1 | 21 / 6 | |
| 1.3.0 | 21 / 6 | |
| 1.2.0 | 21 / 6 | |
| 0.5.1 | 28 / 5 | |
| 0.5.0 | 28 / 5 | |
| 0.4.1 | 28 / 5 | |
| 0.4.0 | 28 / 5 | |
| 0.3.1 | 26 / 5 | |
| 0.3.0 | 26 / 5 | |
| 0.2.4 | 19 / 5 | |
| 0.2.3 | 19 / 5 | |
| 0.2.2 | 19 / 5 | |
| 0.2.1 | 19 / 5 | |
| 0.2.0 | 19 / 5 | |
| 0.1.0 | 19 / 5 | |
| 0.0.4 | 19 / 5 | |
| 0.0.3 | 19 / 5 | |
| 0.0.2 | 19 / 5 |
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.