@things-factory/dataset MIT 22 versions

@things-factory/dataset

npm Repository

module for handling data collection

22

Versions

MIT

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

woo_ramjyp220heartyohhorwengliang95nalshya113shortstopyoungwookwengliang95

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Migration file loader pattern; resolves local filesystem paths, stable across versions of this package.	ai	2026/06/01
provenance	no-provenance	AI (provenance): Established org package; provenance not used across this ecosystem.	ai	2026/05/31
phantom-deps	phantom-dep:statistics	AI (phantom-deps): Declared dep used via config/indirect reference; stable false positive for this package.	ai	2026/05/31
phantom-deps	phantom-dep:@things-factory/personalization	AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/05/31

Versions (showing 22 of 22)

Version	Deps	Published
9.2.24	28 / 0	2026-05-15
9.2.19	28 / 0	2026-04-28
9.0.24	28 / 0	2025-07-30
9.0.19	28 / 0	2025-07-23
8.0.92	28 / 0	2026-04-23
8.0.90	28 / 0	2026-04-10
4.3.815	9 / 0	2026-04-16
4.3.767	9 / 0	2026-01-29
4.3.764	9 / 0	2026-01-28
4.3.755	9 / 0	2026-01-20
4.3.752	9 / 0	2026-01-15
4.3.743	9 / 0	2026-01-08
4.3.740	9 / 0	2026-01-05
4.3.738	9 / 0	2025-12-23
4.3.734	9 / 0	2025-12-17
4.3.729	9 / 0	2025-12-16
4.3.727	9 / 0	2025-12-12
4.3.725	9 / 0	2025-12-11
4.3.723	9 / 0	2025-12-11
4.3.705	9 / 0	2025-12-10
4.3.695	9 / 0	2025-11-21
4.3.689	9 / 0	2025-11-02

v9.2.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.92

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.90

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.815

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.767

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.764

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.755

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.752

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.743

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.740

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.738

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.734

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.729

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.727

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.725

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.723

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.705

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.695

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.3.689

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.