Case file No.468 · pypi · stdio

com.mcparmory/perigon

com.mcparmory/perigon · v1.0.3

Search real-time news articles, companies, journalists, and trending topics

Package ↗GitHub ↗

Security score

78/100

Good

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance10/20

last push 165 days ago

Source transparency10/15

public repo, license unknown/none

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

148 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v1.0.3)Oct 24, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is com.mcparmory/perigon safe?

MCPWatch gives com.mcparmory/perigon a heuristic security score of 78/100 (good), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does com.mcparmory/perigon have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package mcparmory-perigon. That is not proof of safety.

When was com.mcparmory/perigon last updated?

The latest registry version is 1.0.3, published May 12, 2026. The last push to mcparmory/registry was on May 12, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does com.mcparmory/perigon use?

GitHub did not detect a license for mcparmory/registry.

Related servers

same publisher / similar score