← Home

@things-factory/system-base

25
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

nalshya113woo_ramjinwon_in_hatiojyp220heartyohhorwengliang95chris_lim7150joekingayeon4041jinwon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Long-lived org package; provenance absence is consistent across all prior versions. ai
phantom-deps phantom-dep:@things-factory/shell AI (phantom-deps): Same-org monorepo dependency; declared as runtime dep, phantom-dep is a stable false positive for this package. ai

Versions (showing 25 of 25)

Version Deps Published
4.3.815 1 / 0
4.3.767 1 / 0
4.3.764 1 / 0
4.3.755 1 / 0
4.3.752 1 / 0
4.3.743 1 / 0
4.3.740 1 / 0
4.3.738 1 / 0
4.3.734 1 / 0
4.3.729 1 / 0
4.3.727 1 / 0
4.3.725 1 / 0
4.3.723 1 / 0
4.3.705 1 / 0
4.3.695 1 / 0
4.3.689 1 / 0
4.3.675 1 / 0
4.3.673 1 / 0
4.3.672 1 / 0
4.3.671 1 / 0
4.3.591 1 / 0
4.3.535 1 / 0
4.3.534 1 / 0
4.3.533 1 / 0
4.3.526 1 / 0

v4.3.591

1 finding
INFO No provenance attestation provenance

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

v4.3.535

1 finding
INFO No provenance attestation provenance

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

v4.3.534

1 finding
INFO No provenance attestation provenance

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

v4.3.533

1 finding
INFO No provenance attestation provenance

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

v4.3.526

1 finding
INFO No provenance attestation provenance

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