@juspay/blend-design-system
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tanstack/react-virtual | AI (phantom-deps): Component library re-exports UI primitives; phantom-deps are stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:radix-ui | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:sonner | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:@monaco-editor/react | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-popover | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-tooltip | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:@types/styled-components | AI (phantom-deps): Framework-scoped type package; stable pattern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-accordion | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Component library re-exports UI dependencies; stable pattern. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.0.36 | 23 / 38 | |
| 0.0.35 | 22 / 38 | |
| 0.0.34 | 22 / 38 | |
| 0.0.33 | 22 / 38 | |
| 0.0.32 | 22 / 38 | |
| 0.0.31 | 20 / 38 | |
| 0.0.30 | 20 / 38 | |
| 0.0.29 | 20 / 38 | |
| 0.0.28 | 21 / 39 | |
| 0.0.27 | 21 / 39 | |
| 0.0.26 | 21 / 39 | |
| 0.0.25 | 20 / 39 | |
| 0.0.24 | 17 / 39 | |
| 0.0.23 | 15 / 39 | |
| 0.0.22 | 15 / 39 | |
| 0.0.21 | 14 / 39 | |
| 0.0.20 | 14 / 39 | |
| 0.0.19 | 14 / 39 | |
| 0.0.18 | 14 / 39 | |
| 0.0.17 | 14 / 39 | |
| 0.0.16 | 14 / 39 | |
| 0.0.15 | 14 / 39 | |
| 0.0.14 | 14 / 39 | |
| 0.0.13 | 14 / 39 | |
| 0.0.12 | 14 / 39 | |
| 0.0.11 | 14 / 39 | |
| 0.0.10 | 14 / 39 | |
| 0.0.9 | 14 / 39 | |
| 0.0.8 | 14 / 39 | |
| 0.0.7 | 14 / 39 | |
| 0.0.6 | 14 / 39 | |
| 0.0.5 | 14 / 39 | |
| 0.0.1 | 14 / 26 |
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.