npm · registry.npmjs.org

@hookfish/provider

Suspicious Publish Context

Why PkgRadar flagged 0.1.0

Severity	Signal	Evidence
medium	Suspicious Publish Context	—

Showing signal labels only. Sign in to view the exact matched indicators for each finding.

Scanned versions

Version	Verdict	Score	Scanned (UTC)
`0.6.0`	Low risk	0	2026-08-14
`0.6.0-canary-8c7c612`	Low risk	0	2026-08-14
`0.5.0`	Low risk	0	2026-08-13
`0.5.0-canary-d4495a1`	Low risk	0	2026-08-13
`0.5.0-canary-ee51ebd`	Low risk	0	2026-08-13
`0.4.0`	Low risk	0	2026-08-12
`0.4.0-canary-4226c6b`	Low risk	0	2026-08-12
`0.4.0-canary-3602b04`	Low risk	0	2026-08-12
`0.3.0`	Low risk	0	2026-08-12
`0.3.0-canary-835e874`	Low risk	0	2026-08-12
`0.3.0-canary-796722e`	Low risk	0	2026-08-12
`0.2.0`	Low risk	0	2026-08-12
`0.1.0`	Review	10	2026-08-12
`0.2.0-canary-397067d`	Low risk	0	2026-08-12

Block this in CI

PkgRadar gates @hookfish/provider (and every other dependency) before it merges. One line in your pipeline:

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

Prefer zero config? Install the GitHub App and it gates every pull request automatically — no pipeline edits, no API key.

Loading the latest scan…