Prizm Pulse installs statistics
By DQLABS · GitHub Marketplace
GitHub app for Prizm that tracks impacted assets on PR merge by analyzing model changes for lineage and root cause analysis
Prizm Pulse has 5 recorded installs on GitHub Marketplace.
It ranks #1160 of 1,410 tracked GitHub Marketplace listings by installs.
PluginStats has 1 daily observations since Oct 19, 2026; the latest is from Oct 19, 2026.
About Prizm Pulse
GitHub Application Integration for dbt Projects (Prizm)
This GitHub application continuously captures pull request (PR) and commit-level changes from your dbt repositories, stores them in your database, and makes them available to the Investigation Agent. When an alert triggers, the agent correlates the alert with recent code changes and lineage context to generate a root-cause hypothesis—including the exact PR, files, authors, and downstream impact.
How it works (end-to-end)
• Capture PR • Monitors PR open/merge events and associated commits. • Detects changes to .sql and .yml files (typically under models/ and seeds/). • Extract + persist change metadata • Parses diffs to identify: • Models/assets changed • What changed (SQL/YAML diff signals) • PR + commit details (PR number/link, author, timestamps, branch) • Stores this metadata in your database as an auditable change log. • Lineage-aware investigation • When an alert occurs, the Investigation Agent: • Starts from the impacted downstream asset(s) • Traverses upstream through lineage to find the most likely originating change • Checks for recent PRs/commits touching any upstream models in the path • Produces a ranked root-cause hypothesis tied back to the exact PR(s)
Key features
• Automated change tracking across PRs/commits • Lineage traversal (upstream + downstream) to connect one code change to many impacted models • Root-cause hypothesis generation that links alerts to: • PR number + link • Changed files and models • Author and time of change • Downstream assets affected
Example insight
• “Alert on order_invoice.amount likely caused by PR #42 (merged 2 hours ago) which modified models/orders.sql; downstream lineage shows order_invoice depends on orders.”
Benefits
• Accelerates root-cause analysis for data incidents by connecting alerts to recent code changes • Improves visibility and accountability with a clear, auditable PR-to-asset change history • Strengthens governance and collaboration in dbt-driven environments
Description from the GitHub Marketplace listing.
- Code review
Where Prizm Pulse sits in the listing
Each band is one page of 20. Installs on a log scale. Placement is projected from installs, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (1)Similar GitHub Marketplace plugins
Data source
Install counts (installations of each GitHub App across accounts and organizations) are read from public GitHub Marketplace listing pages. GitHub does not publish ratings. Category positions reflect GitHub's own popularity sort.
Listing: https://github.com/marketplace/prizm-pulse. First seen Oct 19, 2026; last successful collection Oct 19, 2026. See the methodology.