@blueking/monitor-apm-log
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): New maintainer matched by email as known prior maintainer; manual publish, not compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is a longstanding characteristic of this internal package, not spam. | ai | |
| source-diff | encoded-string-file:main.js | AI (source-diff): Long strings are Unicode BiDi lookup tables from CodeMirror/lezer — legitimate text-processing data, not obfuscation. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.3.30 | 0 / 0 | |
| 2.3.29 | 0 / 0 | |
| 2.3.28 | 0 / 0 | |
| 2.3.27 | 0 / 0 | |
| 2.3.26 | 0 / 0 | |
| 2.3.25 | 0 / 0 | |
| 2.3.24 | 0 / 0 | |
| 2.3.23 | 0 / 0 | |
| 2.3.22 | 0 / 0 | |
| 2.3.21 | 0 / 0 | |
| 2.3.20 | 0 / 0 | |
| 2.3.19 | 0 / 0 | |
| 2.3.18 | 0 / 0 | |
| 2.3.17 | 0 / 0 | |
| 2.3.16 | 0 / 0 | |
| 2.3.15 | 0 / 0 | |
| 2.3.14 | 0 / 0 | |
| 2.3.13 | 0 / 0 | |
| 2.3.12 | 0 / 0 | |
| 2.3.11 | 0 / 0 | |
| 2.3.10 | 0 / 0 | |
| 2.3.9 | 0 / 0 | |
| 2.3.8 | 0 / 0 | |
| 2.3.7 | 0 / 0 | |
| 2.3.6 | 0 / 0 | |
| 2.3.5 | 0 / 0 | |
| 2.3.4 | 0 / 0 | |
| 2.3.3 | 0 / 0 | |
| 2.3.2 | 0 / 0 | |
| 2.3.1 | 0 / 0 | |
| 2.3.0 | 0 / 0 | |
| 2.2.0 | 0 / 0 | |
| 2.1.0 | 0 / 0 | |
| 2.0.2 | 0 / 0 |
v2.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
3 findingsAll previous maintainers (blueking) were replaced by new maintainers (blueking-magicbox). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blueking-magicbox) than the most recent previously approved version (blueking) on 2026-02-27, but blueking-magicbox is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.10
3 findingsAll previous maintainers (blueking) were replaced by new maintainers (blueking-magicbox). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blueking-magicbox) than the most recent previously approved version (blueking) on 2026-02-27, but blueking-magicbox is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.9
3 findingsAll previous maintainers (blueking) were replaced by new maintainers (blueking-magicbox). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blueking-magicbox) than the most recent previously approved version (blueking) on 2026-02-09, but blueking-magicbox is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.8
3 findingsAll previous maintainers (blueking) were replaced by new maintainers (blueking-magicbox). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (blueking-magicbox) than the most recent previously approved version (blueking) on 2026-02-06, but blueking-magicbox is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.