← Home

@things-factory/process

npm Repository

Module to manage the business processes

23
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, 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:moment-timezone AI (phantom-deps): Config-referenced dep pattern consistent with this org's packages. ai
phantom-deps phantom-dep:@things-factory/worklist AI (phantom-deps): Same-org monorepo dep referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@things-factory/organization AI (phantom-deps): Same-org monorepo dep referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@things-factory/board-service AI (phantom-deps): Same-org monorepo dep referenced in config; stable false positive for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Migration file loader pattern iterating local filesystem paths; not arbitrary module loading. ai
phantom-deps phantom-dep:@things-factory/scheduler-client AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@operato/event-view AI (phantom-deps): Same-ecosystem dependency referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@operato/grist-editor AI (phantom-deps): Same-ecosystem dependency referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@things-factory/context-ui AI (phantom-deps): Same-org dependency referenced in config; stable false positive for this package. ai

Versions (showing 23 of 23)

Version Deps Published
9.2.33 9 / 0
9.2.30 9 / 0
9.2.29 9 / 0
9.2.19 9 / 0
9.2.17 9 / 0
9.2.16 9 / 0
9.2.13 9 / 0
9.2.5 9 / 0
9.1.19 9 / 0
9.1.13 9 / 0
9.1.0 9 / 0
9.0.41 9 / 0
9.0.36 9 / 0
9.0.34 9 / 0
9.0.25 9 / 0
9.0.24 9 / 0
9.0.20 9 / 0
9.0.5 9 / 0
9.0.2 9 / 0
9.0.0 9 / 0
8.0.90 12 / 0
8.0.88 12 / 0
6.4.10 13 / 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.

v9.2.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 2026-03-06, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v9.0.34

1 finding
LOW No provenance attestation provenance

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

v9.0.25

1 finding
LOW No provenance attestation provenance

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

v9.0.24

1 finding
LOW No provenance attestation provenance

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

v9.0.20

1 finding
LOW No provenance attestation provenance

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

v9.0.5

1 finding
LOW No provenance attestation provenance

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

v9.0.2

1 finding
LOW No provenance attestation provenance

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

v9.0.0

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.