Case file No.413 · pypi · stdio

dbt-plan

io.github.PresentJay/dbt-plan · v0.18.1

Predicts the DDL a dbt change will execute, before you run it. Reads files, not the warehouse.

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 10 days ago

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

266 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.18.1)Oct 17, 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 dbt-plan safe?

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

Does dbt-plan have known CVEs or vulnerabilities?

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

When was dbt-plan last updated?

The latest registry version is 0.18.1, published Oct 10, 2026. The last push to PresentJay/dbt-plan was on Oct 10, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does dbt-plan use?

GitHub reports the license of PresentJay/dbt-plan as Apache-2.0.

Related servers

same publisher / similar score