← Home

@things-factory/export-ui-csv

npm Repository
15
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

woo_ramjyp220heartyohhorwengliang95nalshya113shortstopyoungwookwengliang95

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@things-factory/export-ui AI (phantom-deps): Same-org monorepo package; phantom-dep false positive stable across versions. ai
phantom-deps phantom-dep:@things-factory/layout-base AI (phantom-deps): Same-org monorepo package; phantom-dep false positive stable across versions. ai

Versions (showing 15 of 15)

Version Deps Published
9.2.33 3 / 0
9.2.29 3 / 0
9.2.24 3 / 0
9.1.19 3 / 0
9.1.0 3 / 0
9.0.41 3 / 0
9.0.34 3 / 0
9.0.25 3 / 0
9.0.24 3 / 0
9.0.20 3 / 0
9.0.5 3 / 0
9.0.0 3 / 0
4.3.815 3 / 0
4.3.705 3 / 0
4.3.695 3 / 0

v9.2.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.705

2 findings
HIGH Publisher changed: heartyoh → wengliang95 (on 2025-12-10) provenance

This version was published by a different npm account than previous versions on 2025-12-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.695

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: heartyoh → horwengliang95 (on 2025-11-21, known maintainer) provenance

This version was published by a different npm account (horwengliang95) than the most recent previously approved version (heartyoh) on 2025-11-21, but horwengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.