@zauru-sdk/components
Componentes reutilizables en las WebApps de Zauru.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): Referenced in config files only; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:react-select | AI (phantom-deps): Referenced in config files only; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@reduxjs/toolkit | AI (phantom-deps): Referenced in config files only; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@zauru-sdk/utils | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:styled-components | AI (phantom-deps): Referenced in config files only; stable false positive for this UI component package. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 22 / 9 | |
| 6.0.0 | 22 / 9 | |
| 2.33.0 | 20 / 9 | |
| 2.32.4 | 20 / 9 | |
| 2.32.3 | 20 / 9 | |
| 2.32.2 | 20 / 9 | |
| 2.32.1 | 20 / 9 | |
| 2.32.0 | 20 / 9 | |
| 2.31.1 | 20 / 9 | |
| 2.31.0 | 20 / 9 | |
| 2.30.0 | 20 / 9 | |
| 2.29.0 | 20 / 9 | |
| 2.28.0 | 20 / 9 | |
| 2.27.0 | 20 / 9 | |
| 2.26.3 | 20 / 9 | |
| 2.25.4 | 20 / 9 | |
| 2.25.3 | 20 / 9 | |
| 2.25.2 | 20 / 9 | |
| 2.25.1 | 20 / 9 | |
| 2.25.0 | 20 / 9 | |
| 2.24.0 | 20 / 9 | |
| 2.23.1 | 20 / 9 | |
| 2.23.0 | 20 / 9 | |
| 2.22.0 | 20 / 9 | |
| 2.21.0 | 20 / 9 | |
| 2.20.0 | 20 / 9 | |
| 2.19.1 | 20 / 9 | |
| 2.19.0 | 20 / 9 | |
| 2.18.4 | 20 / 9 | |
| 2.17.0 | 20 / 9 | |
| 2.16.1 | 20 / 9 | |
| 2.16.0 | 20 / 9 | |
| 2.15.1 | 20 / 9 | |
| 2.15.0 | 20 / 9 | |
| 2.14.2 | 20 / 9 | |
| 2.14.1 | 20 / 9 | |
| 2.14.0 | 20 / 9 | |
| 2.11.0 | 20 / 9 | |
| 2.10.0 | 20 / 9 | |
| 2.9.0 | 20 / 9 | |
| 2.8.0 | 20 / 9 | |
| 2.7.0 | 20 / 9 | |
| 2.6.0 | 20 / 9 | |
| 2.5.0 | 20 / 9 | |
| 2.4.0 | 20 / 9 | |
| 2.3.1 | 20 / 9 | |
| 2.3.0 | 20 / 9 | |
| 2.2.0 | 20 / 9 | |
| 2.1.1 | 20 / 9 | |
| 2.1.0 | 20 / 9 | |
| 2.0.232 | 20 / 9 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.