@vuu-ui/vuu-table-extras
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@salt-ds/lab | AI (dependencies): Alpha dep is a known, stable dependency pattern across this package family's versions. | ai | |
| provenance | missing-githead | AI (provenance): Active monorepo package with clean version history; missing gitHead is a CI config change, not a malware indicator. | ai | |
| dependencies | unvetted-dep:@vuu-ui/vuu-data-react | AI (dependencies): Same @vuu-ui org monorepo dep; consistent pattern across all approved versions of this package family. | ai | |
| source-diff | obfuscated-file:esm/column-settings-panel/ColumnSettingsPanel.css.js | AI (source-diff): CSS-in-JS module with inline SVG data URIs; long lines are expected build output for this UI library. | ai | |
| source-diff | obfuscated-file:cjs/column-settings-panel/ColumnSettingsPanel.css.js | AI (source-diff): CSS-in-JS module with inline SVG data URIs; long lines are expected build output for this UI library. | ai | |
| source-diff | obfuscated-file:cjs/table-settings-panel/TableSettingsPanel.css.js | AI (source-diff): CSS-in-JS module with inline SVG data URIs; long lines are expected build output for this UI library. | ai | |
| source-diff | obfuscated-file:esm/table-settings-panel/TableSettingsPanel.css.js | AI (source-diff): CSS-in-JS module with inline SVG data URIs; long lines are expected build output for this UI library. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package pattern; no description is expected across all @vuu-ui packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is normal for this package family. | ai | |
| phantom-deps | phantom-dep:@vuu-ui/vuu-popups | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for monorepo re-exports. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 2.1.5 | 13 / 2 | |
| 2.1.2 | 13 / 2 | |
| 2.1.0 | 13 / 2 | |
| 2.0.0 | 13 / 2 | |
| 1.0.3 | 12 / 2 | |
| 1.0.2 | 12 / 2 | |
| 1.0.1 | 12 / 2 | |
| 1.0.0 | 12 / 2 | |
| 0.13.118 | 12 / 2 | |
| 0.13.117 | 12 / 2 | |
| 0.13.116 | 12 / 2 | |
| 0.13.115 | 12 / 2 | |
| 0.13.114 | 12 / 2 | |
| 0.13.113 | 12 / 2 | |
| 0.13.112 | 12 / 2 | |
| 0.13.111 | 12 / 2 | |
| 0.13.110 | 12 / 2 | |
| 0.13.109 | 12 / 2 | |
| 0.13.108 | 12 / 2 | |
| 0.13.107 | 12 / 2 | |
| 0.13.106 | 12 / 2 | |
| 0.13.105 | 12 / 2 | |
| 0.13.104 | 12 / 2 | |
| 0.13.103 | 12 / 2 | |
| 0.13.102 | 12 / 2 | |
| 0.13.101 | 12 / 2 | |
| 0.13.100 | 12 / 2 | |
| 0.13.99 | 12 / 2 | |
| 0.13.98 | 12 / 2 | |
| 0.13.97 | 12 / 2 | |
| 0.13.96 | 12 / 2 | |
| 0.13.95 | 12 / 2 | |
| 0.13.93 | 12 / 2 | |
| 0.13.92 | 12 / 2 | |
| 0.13.91 | 12 / 2 | |
| 0.13.90 | 12 / 2 | |
| 0.13.89 | 12 / 2 | |
| 0.13.88 | 12 / 2 | |
| 0.13.87 | 12 / 2 | |
| 0.13.86 | 12 / 2 | |
| 0.13.85 | 12 / 2 | |
| 0.13.84 | 12 / 2 | |
| 0.13.83 | 12 / 2 | |
| 0.13.82 | 12 / 2 | |
| 0.13.81 | 12 / 2 | |
| 0.13.80 | 12 / 2 | |
| 0.13.79 | 12 / 2 | |
| 0.13.78 | 12 / 2 | |
| 0.13.77 | 12 / 2 | |
| 0.13.76 | 12 / 2 | |
| 0.13.75 | 12 / 2 |
v2.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
6 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.118
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.117
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.115
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.114
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.113
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.111
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.110
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.