@things-factory/import-ui-excel
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 the canonical spreadsheet library; its use is expected and appropriate for an Excel import UI package. | ai | |
| phantom-deps | phantom-dep:@things-factory/layout-base | AI (phantom-deps): Same org scope; likely used indirectly via build/bundle pipeline, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:xlsx | AI (phantom-deps): xlsx is referenced in config/build context for this Excel import UI package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Declared for config/peer usage in a monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/import-ui | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires due to indirect/config usage, not a real concern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.2.19 | 3 / 0 | |
| 9.2.16 | 3 / 0 | |
| 9.1.13 | 3 / 0 | |
| 8.0.87 | 3 / 0 | |
| 8.0.74 | 3 / 0 | |
| 8.0.64 | 3 / 0 | |
| 6.4.8 | 3 / 0 | |
| 4.3.790 | 3 / 0 | |
| 4.3.752 | 3 / 0 | |
| 4.3.723 | 3 / 0 | |
| 4.3.701 | 3 / 0 | |
| 4.3.700 | 3 / 0 | |
| 4.3.695 | 3 / 0 | |
| 4.3.689 | 3 / 0 |
v9.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.13
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.
v8.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.790
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.752
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.723
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.701
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.700
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.695
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.