← Home

@blueking/monitor-trace-log

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

blueking-magicbox

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:main.js AI (source-diff): Long strings are Unicode BiDi lookup tables from CodeMirror, a stable false positive for this package. ai

Versions (showing 20 of 20)

Version Deps Published
2.0.26 0 / 0
2.0.25 0 / 0
2.0.24 0 / 0
2.0.23 0 / 0
2.0.22 0 / 0
2.0.21 0 / 0
2.0.20 0 / 0
2.0.19 0 / 0
2.0.18 0 / 0
2.0.17 0 / 0
2.0.16 0 / 0
2.0.15 0 / 0
2.0.14 0 / 0
2.0.13 0 / 0
2.0.12 0 / 0
2.0.11 0 / 0
2.0.10 0 / 0
2.0.9 0 / 0
2.0.8 0 / 0
2.0.7 0 / 0

v2.0.26

1 finding
LOW No provenance attestation provenance

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

v2.0.25

1 finding
LOW No provenance attestation provenance

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

v2.0.8

1 finding
LOW No provenance attestation provenance

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

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