@tomd4vs/prumo

npm · v0.9.5

Is your documentation still true? Checks the context files your coding agent reads against the code. Five high-precision checks, two reports, zero dependencies.

Findings (1)

MED PKG_NEW — @tomd4vs/prumo was first published less than 30 days ago. Very new packages carry elevated supply-chain risk.

Embed this badge

[![MCP security](https://vulnrable.com/api/mcpbadge?pkg=%40tomd4vs%2Fprumo&eco=npm)](https://vulnrable.com/mcp/tomd4vs--prumo/)

Source repo Registry page Check your own config →

Automated registry-metadata scan; not a code audit. Findings come from npm metadata published by the package owner and from public security advisories (OSV/GHSA) — not from our own assessment of the code.
Grade scanned 2026-09-14 · package count resolved 2026-08-18. A package fixed after that date will still show its earlier grade here.
Maintainer and think this is wrong or out of date? Get in touch — corrections are welcome.