@things-factory/qc MIT 51 versions

@things-factory/qc

npm Repository

module for handling QC (Quality Control)

51

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
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped monorepo package for Quality Control; name similarity to 'qs' is coincidental and not a squatting attempt.	ai	2026/05/23
typosquat	typosquat.levenshtein:pg	AI (typosquat): Same rationale; 2-edit distance to 'pg' is not meaningful for a scoped QC module in a large monorepo.	ai	2026/05/23
phantom-deps	phantom-dep:@operato/dataset	AI (phantom-deps): Declared dep used via config/build tooling in monorepo context; stable false positive for this package.	ai	2026/05/23
phantom-deps	phantom-dep:@things-factory/shell	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here.	ai	2026/05/23

Versions (showing 51 of 73)

View all versions

Version	Deps	Published
9.2.24	3 / 0	2026-05-15
9.2.23	3 / 0	2026-05-11
9.2.22	3 / 0	2026-05-11
9.2.21	3 / 0	2026-05-11
9.2.20	3 / 0	2026-05-08
9.2.19	3 / 0	2026-04-28
9.2.18	3 / 0	2026-04-14
9.2.17	3 / 0	2026-04-01
9.2.16	3 / 0	2026-03-25
9.2.13	3 / 0	2026-03-19
9.2.5	3 / 0	2026-03-06
9.1.19	3 / 0	2025-11-25
9.1.18	3 / 0	2025-10-28
9.1.17	3 / 0	2025-10-24
9.1.16	3 / 0	2025-10-23
9.1.15	3 / 0	2025-10-23
9.1.14	3 / 0	2025-10-22
9.1.13	3 / 0	2025-10-22
9.1.12	3 / 0	2025-10-22
9.1.8	3 / 0	2025-10-21
9.1.7	3 / 0	2025-10-20
9.1.6	3 / 0	2025-10-15
9.1.5	3 / 0	2025-10-14
9.1.4	3 / 0	2025-10-13
9.1.3	3 / 0	2025-10-10
9.1.1	3 / 0	2025-09-24
9.1.0	3 / 0	2025-09-16
9.0.41	3 / 0	2025-09-14
9.0.38	3 / 0	2025-09-08
9.0.37	3 / 0	2025-09-08
9.0.36	3 / 0	2025-09-06
9.0.35	3 / 0	2025-09-02
9.0.34	3 / 0	2025-09-01
9.0.33	3 / 0	2025-08-13
9.0.32	3 / 0	2025-08-06
9.0.28	3 / 0	2025-08-02
9.0.27	3 / 0	2025-08-01
9.0.26	3 / 0	2025-08-01
9.0.25	3 / 0	2025-08-01
9.0.24	3 / 0	2025-07-30
9.0.20	3 / 0	2025-07-23
9.0.19	3 / 0	2025-07-23
9.0.15	3 / 0	2025-07-19
9.0.14	3 / 0	2025-07-19
9.0.13	3 / 0	2025-07-17
9.0.12	3 / 0	2025-07-17
9.0.9	3 / 0	2025-07-15
9.0.7	3 / 0	2025-07-14
9.0.6	3 / 0	2025-07-06
9.0.5	3 / 0	2025-07-05
9.0.4	3 / 0	2025-07-05

v9.2.24

1 finding

LOW No provenance attestation provenance

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

v9.2.23

1 finding

LOW No provenance attestation provenance

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

v9.2.22

1 finding

LOW No provenance attestation provenance

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

v9.2.21

1 finding

LOW No provenance attestation provenance

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

v9.2.20

1 finding

LOW No provenance attestation provenance

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

v9.2.18

1 finding

LOW No provenance attestation provenance

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

v9.2.17

1 finding

LOW No provenance attestation provenance

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

v9.2.16

1 finding

LOW No provenance attestation provenance

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

v9.2.13

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: nalshya113 → heartyoh (on 2026-03-19, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (nalshya113) on 2026-03-19, but heartyoh 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.

v9.2.5

1 finding

LOW No provenance attestation provenance

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

v9.1.19

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: nalshya113 → heartyoh (on 2025-11-25, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (nalshya113) on 2025-11-25, but heartyoh 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.

v9.1.18

1 finding

LOW No provenance attestation provenance

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

v9.1.17

1 finding

LOW No provenance attestation provenance

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

v9.1.16

1 finding

LOW No provenance attestation provenance

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

v9.1.15

1 finding

LOW No provenance attestation provenance

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

v9.1.14

1 finding

LOW No provenance attestation provenance

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

v9.1.13

1 finding

LOW No provenance attestation provenance

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

v9.1.12

1 finding

LOW No provenance attestation provenance

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

v9.1.8

1 finding

LOW No provenance attestation provenance

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

v9.1.7

1 finding

LOW No provenance attestation provenance

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

v9.1.6

1 finding

LOW No provenance attestation provenance

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

v9.1.5

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 → nalshya113 (on 2025-10-14, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-14, but nalshya113 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.

v9.1.4

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 → nalshya113 (on 2025-10-13, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-13, but nalshya113 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.

v9.1.3

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 → nalshya113 (on 2025-10-10, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-10, but nalshya113 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.

v9.1.1

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 → nalshya113 (on 2025-09-24, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-09-24, but nalshya113 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.

v9.1.0

1 finding

LOW No provenance attestation provenance

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

v9.0.41

1 finding

LOW No provenance attestation provenance

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

v9.0.38

1 finding

LOW No provenance attestation provenance

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

v9.0.37

1 finding

LOW No provenance attestation provenance

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

v9.0.36

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.35

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.34

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.33

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.32

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.28

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.27

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.26

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.25

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.20

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.

v9.0.15

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.14

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.13

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.12

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.9

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.7

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.6

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.5

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.4

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.