@fiscozen/table
Design System Table component
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal design system component; sparse metadata is consistent across the @fiscozen org, not a spam signal. | ai | |
| phantom-deps | phantom-dep:@fiscozen/input | AI (phantom-deps): Same-org component; phantom-dep heuristic unreliable for bundled Vue component libraries. | ai | |
| phantom-deps | phantom-dep:@fiscozen/radio | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/button | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/dialog | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/checkbox | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/dropdown | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/progress | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fiscozen/composables | AI (phantom-deps): Same-org component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for bundled output. | ai | |
| phantom-deps | phantom-dep:@types/ramda | AI (phantom-deps): Type-only dep; phantom-dep heuristic not applicable. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.1.8 | 13 / 23 | |
| 2.1.7 | 13 / 23 | |
| 2.1.6 | 13 / 23 | |
| 2.1.5 | 13 / 23 | |
| 2.1.4 | 13 / 23 | |
| 2.1.3 | 13 / 23 | |
| 2.1.2 | 13 / 23 | |
| 2.1.1 | 13 / 23 | |
| 2.1.0 | 13 / 23 | |
| 2.0.6 | 13 / 23 | |
| 2.0.5 | 13 / 23 | |
| 2.0.4 | 13 / 23 | |
| 2.0.3 | 13 / 23 | |
| 2.0.2 | 13 / 23 | |
| 2.0.1 | 13 / 23 | |
| 2.0.0 | 13 / 23 | |
| 1.0.0 | 13 / 23 | |
| 0.1.18 | 13 / 23 | |
| 0.1.16 | 13 / 23 | |
| 0.1.15 | 13 / 23 | |
| 0.1.14 | 13 / 23 | |
| 0.1.13 | 14 / 23 | |
| 0.1.12 | 2 / 23 |
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.