← Home

@sentio/chain

npm

Chain utils

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

longwallendragonphilz3906pooytr1rnonslzx_lizixingfrozenluo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): only-allow pnpm is a standard package manager enforcement pattern; stable for this package. ai
typosquat typosquat.levenshtein:chalk AI (typosquat): Scoped @sentio org package; Levenshtein match to chalk is coincidental, not a typosquat. ai
semgrep semgrep:shady-links-tlds AI (semgrep): Fires on blockchain explorer URLs in chain metadata (e.g. mantlescan.xyz); not C2 or exfiltration. ai
bogus-package bogus-package AI (bogus-package): Monorepo utility package; missing repo/keywords/deps fields are consistent with its structure across 123 versions. ai

Versions (showing 51 of 51)

Version Deps Published
3.4.34 0 / 0
3.4.33 0 / 0
3.4.32 0 / 0
3.4.31 0 / 0
3.4.30 0 / 0
3.4.29 0 / 0
3.4.28 0 / 0
3.4.27 0 / 0
3.4.26 0 / 0
3.4.25 0 / 0
3.4.24 0 / 0
3.4.23 0 / 4
3.4.22 0 / 0
3.4.20 0 / 0
3.4.19 0 / 0
3.4.18 0 / 0
3.4.17 0 / 0
3.4.16 0 / 0
3.4.15 0 / 0
3.4.14 0 / 0
3.4.13 0 / 0
3.4.12 0 / 0
3.4.11 0 / 0
3.4.10 0 / 0
3.4.9 0 / 0
3.4.8 0 / 0
3.4.7 0 / 0
3.4.6 0 / 0
3.4.5 0 / 0
3.4.4 0 / 0
3.4.3 0 / 0
3.4.2 0 / 0
3.4.1 0 / 0
3.4.0 0 / 0
3.3.3 0 / 0
3.3.2 0 / 0
3.3.1 0 / 0
3.3.0 0 / 0
3.2.1 0 / 0
3.2.0 0 / 0
3.1.0 0 / 0
3.0.9 0 / 4
3.0.8 0 / 0
3.0.7 0 / 0
3.0.6 0 / 0
3.0.5 0 / 0
3.0.4 0 / 0
3.0.3 0 / 0
3.0.2 0 / 0
3.0.1 0 / 0
3.0.0 0 / 0

v3.4.34

1 finding
LOW No provenance attestation provenance

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

v3.4.33

1 finding
LOW No provenance attestation provenance

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

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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