faultline vs pagerduty
faultline is a plugin bundle for AI coding tools published by dlt. Marketplaces we read that list it: 1 (Community GitHub marketplaces). pagerduty is a plugin bundle for AI coding tools published by PagerDuty. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  faultline |  pagerduty |
|---|---|---|
| Community marketplace dlt/faultline | Listed Version: 0.1.0 Forks (GitHub): 7 Stars (GitHub): 86 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | faultline | pagerduty |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 86 (better) | 7 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.pagerduty.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 16 | 3 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/dlt/faultline | github.com/pagerduty/claude-code-plugins |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 9 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
faultline
Talk to your Faultline error tracker from Claude Code — query error groups, occurrences, captured locals, and APM traces while debugging.
pagerduty
Enhance code quality and security through PagerDuty risk scoring and incident correlation. Score pre-commit diffs against historical incident data and surface deployment risk before you ship.
How to run each
faultline As a Claude Code plugin
/plugin marketplace add dlt/faultline
/plugin install faultline@dlt-faultlinepagerduty As a Claude Code plugin
/plugin install pagerduty@claude-plugins-officialCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only pagerduty has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: faultline · What it can do: pagerduty · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.