All @platformatic/metrics versions
@platformatic/metrics @3.34.0
rejected
This version was rejected.
It did not pass GreenFlagged's security review and is not served by the registry.
The findings and risk dispositions below explain why.
50
Risk Score
Apache-2.0
License
No
Install Scripts
3
Dependencies
3
Dev Dependencies
10.1 KB
Package Size
Published
Platformatic Capability Metrics
Maintainers
mzugmivan-tymoshenkomarcopiraccinileorossishogun_pandamatteo.collinaqardlucamaraschisimone.sanfra
Dependencies (3)
| Package | Constraint | Registry Status |
|---|---|---|
| @platformatic/promotel | ^0.1.0 | auto_approved |
| @platformatic/prom-client | ^1.0.0 | auto_approved |
| @platformatic/http-metrics | ^0.3.0 | auto_approved |
Dev Dependencies (3)
| Package | Constraint | Registry Status |
|---|---|---|
| eslint | 9 | auto_approved |
| neostandard | ^0.12.0 | No greenflagged match |
| cleaner-spec-reporter | ^0.5.0 | Not imported |
Transitive Dependency Tree
21 transitive deps
max depth 4
├─
@platformatic/http-metrics
^0.3.0
→ 0.3.0
├─
@platformatic/prom-client
^1.0.0
→ 1.0.0
├─
@platformatic/promotel
^0.1.0
→ 0.1.0
├─
@opentelemetry/api
^1.4.0
→ 1.9.1
├─
@platformatic/prom-client
^1.0.0
→ 1.0.0
├─
long
^5.3.2
→ 5.3.2
├─
prom-client
^15.1.3
→ 15.1.3
├─
protobufjs
^7.4.0
→ 7.6.1
├─
undici
^6.19.8
→ 6.26.0
├─
@opentelemetry/api
^1.4.0
→ 1.9.1
├─
@protobufjs/aspromise
^1.1.2
→ 1.1.2
├─
@protobufjs/base64
^1.1.2
→ 1.1.2
├─
@protobufjs/codegen
^2.0.5
→ 2.0.5
├─
@protobufjs/eventemitter
^1.1.1
→ 1.1.1
├─
@protobufjs/fetch
^1.1.1
→ 1.1.1
├─
@protobufjs/float
^1.0.2
→ 1.0.2
├─
@protobufjs/inquire
^1.1.2
→ 1.1.2
├─
@protobufjs/path
^1.1.2
→ 1.1.2
├─
@protobufjs/pool
^1.1.0
→ 1.1.0
├─
@protobufjs/utf8
^1.1.1
→ 1.1.1
├─
@types/node
>=13.7.0
→ 25.9.1
├─
long
^5.3.2
→ 5.3.2
├─
tdigest
^0.1.1
├─
@protobufjs/aspromise
^1.1.1
→ 1.1.2
├─
undici-types
>=7.24.0 <7.24.7
→ 7.24.6
Changes from v3.33.0
No metadata changes detected.
File Changes
0 added
0 removed
3 modified
size delta: +4.8 KB
Risk Dispositions (2 applicable to this version, 0 other)
Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.
| Rule | Source | Disposition | Author | Reason | |
|---|---|---|---|---|---|
regressed-provenance |
provenance | reject | AI | AI (provenance): Established package dropped CI provenance attestation; generalizes as a disqualifier until attestation is restored. | |
publisher-changed |
provenance | reject | AI | AI (provenance): Publisher changed from GitHub Actions to a human account alongside dropped attestation; strong compromise signal. |
SAST Findings (2)
HIGH
Provenance attestation missing — previous versions had it
provenance
This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
HIGH
Publisher changed: GitHub Actions → shogun_panda (on 2026-01-29)
provenance
This version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.
Review Summary
Risk score: 50. Findings: 2 high (+50).
Published to npm: