npm · registry.npmjs.org

@hayrem_/mcp-minecraft-forge

New Account With Lifecycle Hook: package first published 0 day(s) ago, 2 total version(s), has lifecycle hook

Why PkgRadar flagged 0.2.6

Severity	Signal	Evidence
high	New Account With Lifecycle Hook	package first published 0 day(s) ago, 2 total version(s), has lifecycle hook · package.json
medium	Suspicious Publish Context	{"package_age_days":0,"publisher":"hayrem_","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

Scanned versions

Version	Verdict	Score	Scanned (UTC)
`0.2.6`	High risk	15	2026-06-17
`0.2.5`	Review	15	2026-06-17
`0.2.3`	High risk	15	2026-06-17
`0.2.4`	High risk	15	2026-06-17
`0.2.2`	High risk	15	2026-06-17
`0.2.1`	High risk	15	2026-06-17
`0.2.0`	High risk	15	2026-06-17
`0.1.2`	High risk	15	2026-06-17
`0.1.0`	High risk	15	2026-06-17

Block this in CI

PkgRadar gates @hayrem_/mcp-minecraft-forge (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm @hayrem_/[email protected]