← Home

@things-factory/labeling

npm Repository

Labeling workflow management module for orchestrating end-to-end labeling workflows

5
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

Keywords

things-factorylabelingworkfloworchestrationautomation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:uuid AI (phantom-deps): Monorepo pattern; declared deps may be used indirectly via build/config rather than direct imports. ai
phantom-deps phantom-dep:i18next AI (phantom-deps): Same monorepo pattern; i18next commonly declared at package level but consumed via shared config. ai
phantom-deps phantom-dep:@things-factory/env AI (phantom-deps): Same-org scope; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@things-factory/dataset AI (phantom-deps): Same-org scope; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@things-factory/ai-inference AI (phantom-deps): Same-org scope; stable false positive for this monorepo package. ai

Versions (showing 5 of 5)

Version Deps Published
9.2.27 13 / 0
9.2.26 13 / 0
9.2.25 13 / 0
9.2.20 13 / 0
9.1.19 13 / 0

v9.2.27

1 finding
LOW No provenance attestation provenance

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

v9.2.26

1 finding
LOW No provenance attestation provenance

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

v9.2.25

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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