Case file No.344 · pypi · stdio

TopicForge

io.github.yaniswav/topicforge · v0.7.2

Read-only MCP server for ROS2 and DDS: topics, participants, QoS mismatches, bags.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 1 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

345 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 (v0.7.2)Oct 18, 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 TopicForge safe?

MCPWatch gives TopicForge a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does TopicForge have known CVEs or vulnerabilities?

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

When was TopicForge last updated?

The latest registry version is 0.7.2, published Oct 18, 2026. The last push to yaniswav/TopicForge was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does TopicForge use?

GitHub reports the license of yaniswav/TopicForge as MIT.

Related servers

same publisher / similar score