@things-factory/import-ui-csv
User interface for showing csv import option.
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:xlsx | AI (dependencies): xlsx is a widely-used spreadsheet library; its use in a CSV import UI package is expected and stable across versions. | ai | |
| phantom-deps | phantom-dep:@things-factory/layout-base | AI (phantom-deps): Same org scope; newly added runtime dep, phantom flag is a false positive for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived org package; lack of provenance is consistent across all 901 versions, not a new anomaly. | ai | |
| phantom-deps | phantom-dep:xlsx | AI (phantom-deps): Monorepo component; xlsx referenced in config/build, not direct import — stable false positive. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Same monorepo pattern; layout dep referenced via config, not direct import. | ai | |
| phantom-deps | phantom-dep:@things-factory/import-ui | AI (phantom-deps): Same org scope; peer/re-export pattern in monorepo, stable false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.2.19 | 3 / 0 | |
| 9.2.17 | 3 / 0 | |
| 9.2.13 | 3 / 0 | |
| 8.0.88 | 3 / 0 | |
| 8.0.87 | 3 / 0 | |
| 4.3.815 | 3 / 0 | |
| 4.3.689 | 3 / 0 |
v9.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.815
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.689
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.