@enso-ui/tables
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@enso-ui/enums | AI (dependencies): Same-org dependency in a long-established package family; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@enso-ui/modal | AI (dependencies): Same-org dependency in a long-established package family; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@enso-ui/enums | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/modal | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/loader | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/select | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/switch | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/datepicker | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/directives | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/search-mode | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): FontAwesome peer dep referenced in config, not direct JS import; standard pattern. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): FontAwesome peer dep referenced in config, not direct JS import; standard pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/dropdown | AI (phantom-deps): Same-org SFC component; used via templates/config, not direct JS import. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue SFC library; vue is a peer dep referenced in templates/config, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:v-tooltip | AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.1.29 | 5 / 11 | |
| 4.1.28 | 5 / 11 | |
| 4.1.27 | 5 / 11 | |
| 4.1.25 | 5 / 11 | |
| 4.1.21 | 5 / 11 | |
| 4.1.19 | 5 / 11 | |
| 4.1.18 | 5 / 11 | |
| 4.1.17 | 5 / 11 | |
| 4.1.16 | 5 / 11 | |
| 4.1.15 | 5 / 11 | |
| 4.1.14 | 5 / 11 | |
| 4.1.13 | 5 / 11 | |
| 4.1.12 | 5 / 11 | |
| 4.1.11 | 5 / 11 | |
| 4.1.10 | 5 / 11 | |
| 4.1.9 | 5 / 11 | |
| 4.1.8 | 5 / 11 | |
| 4.1.7 | 5 / 11 | |
| 4.1.6 | 5 / 11 | |
| 4.1.5 | 5 / 11 | |
| 4.1.4 | 5 / 11 | |
| 4.1.3 | 15 / 1 | |
| 4.1.2 | 16 / 0 | |
| 4.1.1 | 16 / 0 | |
| 4.1.0 | 16 / 0 | |
| 4.0.0 | 16 / 0 |
v4.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.