@skbkontur/react-ui
UI Components
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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in ThemeShowcase VariablesCollector for property access tracing — benign introspection, not obfuscation. | ai | |
| dependencies | unvetted-dep:@skbkontur/global-object | AI (dependencies): First-party scoped package from the same skbkontur org; consistent across versions. | ai | |
| phantom-deps | phantom-dep:react-docgen | AI (phantom-deps): react-docgen is listed as a runtime dep but used for tooling/storybook; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package loaded by convention via Babel transform; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.0.7 | 20 / 68 | |
| 6.0.6 | 20 / 68 | |
| 6.0.5 | 20 / 68 | |
| 6.0.4 | 20 / 68 | |
| 6.0.3 | 20 / 68 | |
| 6.0.2 | 20 / 76 | |
| 6.0.1 | 20 / 76 | |
| 6.0.0 | 20 / 76 | |
| 5.6.12 | 20 / 76 | |
| 5.6.11 | 20 / 76 |
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.