@things-factory/export-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@things-factory/layout-base | AI (phantom-deps): Same-org scoped package; used via framework wiring, not direct import. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:xlsx | AI (phantom-deps): xlsx is referenced in config/build context; consistent with Excel export functionality of this package. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Same-org peer dependency used via config/framework wiring, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/export-ui | AI (phantom-deps): Same-org sibling dependency; indirect usage via framework is expected for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 6 / 0 | |
| 9.2.16 | 6 / 0 | |
| 9.1.19 | 6 / 0 | |
| 9.1.13 | 6 / 0 | |
| 9.1.0 | 6 / 0 | |
| 9.0.41 | 6 / 0 | |
| 9.0.25 | 6 / 0 | |
| 9.0.24 | 6 / 0 | |
| 9.0.5 | 6 / 0 | |
| 9.0.0 | 6 / 0 | |
| 8.0.88 | 6 / 0 | |
| 6.4.8 | 6 / 0 | |
| 4.3.815 | 6 / 0 | |
| 4.3.767 | 6 / 0 | |
| 4.3.755 | 6 / 0 | |
| 4.3.752 | 6 / 0 | |
| 4.3.740 | 6 / 0 | |
| 4.3.729 | 6 / 0 | |
| 4.3.723 | 6 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.19
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.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage 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.
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.815
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.767
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.755
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.740
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.729
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.