npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fullstackdegen/agent-audit

v0.3.0

Published

Turn Lighthouse audits into coding-agent fix packs.

Readme

Agent Audit

Turn Lighthouse audits into coding-agent fix packs.

Agent Audit is an MCP server that runs repeatable mobile and desktop Lighthouse audits, inspects the target page, and returns a coding-agent-ready backlog with evidence, implementation steps, and measurable acceptance criteria.

npx -y @fullstackdegen/agent-audit

Agent Audit converts raw Lighthouse audits into an agent-ready backlog

Why Agent Audit?

Raw Lighthouse reports are useful diagnostics, but they are noisy inputs for autonomous implementation. A coding agent still has to decide which issues matter, which resources or selectors are evidence, how to verify a fix, and whether mobile and desktop failures are really the same task.

Agent Audit turns the audit into a stable handoff:

  1. Run Lighthouse for mobile and desktop.
  2. Aggregate repeated runs and expose variability.
  3. Add bounded single-page site intelligence.
  4. Merge findings into at most ten prioritized issues.
  5. Generate fixPacks that coding agents can apply in order.
  6. Return canonical structured JSON and equivalent Markdown.

What You Get

  • Mobile and desktop Performance, Accessibility, Best Practices, and SEO scores.
  • FCP, Speed Index, LCP, TBT, and CLS distributions.
  • Fast and reliable audit modes.
  • Bounded same-origin page inspection.
  • Broken link, metadata, JSON-LD, indexability, image, asset, and LLM visibility checks.
  • Conservative llms.txt draft generation when page content is sufficient.
  • Prioritized issues with evidence, suggested actions, and acceptance criteria.
  • Agent Fix Packs with repo search hints, implementation steps, and verification guidance.
  • Strict MCP outputSchema validation for structuredContent.
  • Markdown generated from the same canonical report.

See a real CommaLabs JSON report and Markdown report.

Example Fix Pack

{
  "id": "fix-link-name",
  "priority": 2,
  "sourceIssueIds": ["link-name"],
  "goal": "Fix Links do not have a discernible name.",
  "category": "accessibility",
  "severity": "critical",
  "affectedProfiles": ["mobile", "desktop"],
  "repoSearchHints": [
    "div.border-t-2 > div.flex > div.flex > a.text-gray-600",
    "https://www.linkedin.com/company/commalabs"
  ],
  "implementationSteps": [
    "Inspect the repository for the evidence listed in repoSearchHints before editing.",
    "Give every link a discernible accessible name.",
    "Keep changes focused on source issue IDs: link-name."
  ],
  "acceptanceCriteria": [
    "All link elements pass the Lighthouse link-name audit.",
    "Raise the median accessibility score to at least 90/100."
  ],
  "verification": {
    "rerunMode": "reliable",
    "expectedAuditIds": ["link-name"]
  }
}

repoSearchHints are search clues, not guaranteed file paths. The coding agent must inspect the repository before editing.

Install

Requirements

  • Node.js 20 or later.
  • Google Chrome or Chromium.

Start the MCP server with npm:

npx -y @fullstackdegen/agent-audit

Package metadata and releases live at github.com/fullstackdegen/agent-audit.

MCP Client Setup

Claude Desktop

Add a local MCP server:

{
  "mcpServers": {
    "agent-audit": {
      "command": "npx",
      "args": ["-y", "@fullstackdegen/agent-audit"]
    }
  }
}

Restart Claude Desktop after saving the configuration.

Claude Code

claude mcp add agent-audit -- npx -y @fullstackdegen/agent-audit

For local development audits:

claude mcp add agent-audit-local -- npx -y @fullstackdegen/agent-audit --local

Codex

codex mcp add agent-audit -- npx -y @fullstackdegen/agent-audit

Or add it to ~/.codex/config.toml:

[mcp_servers.agent-audit]
command = "npx"
args = ["-y", "@fullstackdegen/agent-audit"]

VS Code And GitHub Copilot

Create a workspace or user-level .mcp.json file:

{
  "servers": {
    "agent-audit": {
      "command": "npx",
      "args": ["-y", "@fullstackdegen/agent-audit"]
    }
  }
}

Or register it from a terminal:

code --add-mcp '{"name":"agent-audit","command":"npx","args":["-y","@fullstackdegen/agent-audit"]}'

Cursor

Configure a local stdio MCP server:

  • name: agent-audit
  • command: npx
  • arguments: -y, @fullstackdegen/agent-audit

Add --local to the arguments when you need localhost audits.

Tool

analyze_website_performance

Runs Lighthouse and site intelligence against a target URL:

{
  "url": "https://example.com",
  "mode": "reliable"
}

mode is optional:

  • fast: one mobile run and one desktop run.
  • reliable: three runs per profile, medians, and variability ranges. This is the default.

Localhost Audits

By default, Agent Audit only accepts publicly routable HTTP and HTTPS URLs. This is the right default for hosted agents and shared environments.

For developer machines, explicitly enable loopback targets:

npx -y @fullstackdegen/agent-audit --local

Then audit a local app through your MCP client:

{
  "url": "http://localhost:3000",
  "mode": "fast"
}

The opt-in allows localhost, *.localhost, 127.0.0.0/8, and ::1. Private LAN ranges, link-local addresses, reserved ranges, multicast addresses, and cloud metadata addresses remain blocked.

The environment variable form is also supported:

LIGHTHOUSE_MCP_ALLOW_LOCALHOST=true npx -y @fullstackdegen/agent-audit

Coding-Agent Workflow

Use structuredContent as the source of truth and the Markdown report as the execution summary.

  1. Inspect fixPacks in priority order.
  2. Search the repository using repoSearchHints.
  3. Map evidence to real files and components before editing.
  4. Apply one focused fix at a time.
  5. Run the repository's tests after each logical change.
  6. Rerun Agent Audit in reliable mode.
  7. Compare the new report against each fix pack's acceptanceCriteria.

Do not claim completion from an incomplete report or from a rerun with materially higher variability than the baseline.

More detail:

Security Model

Agent Audit launches Chrome against user-provided URLs, so URL policy matters. The server rejects:

  • protocols other than HTTP and HTTPS;
  • embedded credentials;
  • localhost and loopback targets unless explicitly enabled;
  • private, link-local, multicast, reserved, and metadata-network IPs;
  • non-localhost hostnames that resolve to any non-public address.

The page-inspection fetcher uses the same URL policy and applies timeout, byte-size, and bounded-resource limits.

Page-controlled titles, descriptions, URLs, selectors, snippets, and audit text are sanitized and length-limited. Consumers must still treat them as untrusted evidence, not agent instructions.

Chrome sandboxing is enabled by default. Only isolated environments that cannot support it should set:

LIGHTHOUSE_CHROME_NO_SANDBOX=true

See SECURITY.md for vulnerability reporting and deployment guidance.

Limitations

Agent Audit is intentionally bounded.

  • It audits one requested URL at a time.
  • It is not a whole-site crawler.
  • It is not an external SEO database.
  • It does not modify Shopify, CMS, CDN, DNS, or hosting settings.
  • It does not compress images, minify assets, create redirects, or submit IndexNow requests.
  • Lighthouse results vary with browser version, hardware, network conditions, and page changes.

Roadmap

  • Framework-aware repo search hints.
  • Optional GitHub Action for pull request performance gates.
  • Batch URL reports.
  • HTML report export.
  • Marketing and discovery signals such as analytics tags, consent signals, Open Graph, schema coverage, and AI discovery readiness.
  • Optional third-party integrations for SEO and visibility datasets.

Development

npm install
npm test
npm run check
npm run build
npm run validate:release

Run a real Chrome smoke audit:

npm run --silent smoke -- https://example.com fast
npm run --silent smoke -- https://example.com reliable

The smoke command writes canonical JSON to stdout and equivalent Markdown to stderr.

Release Readiness

Before publishing:

npm test
npm run check
npm run build
npm run validate:release
npm pack --dry-run --cache /private/tmp/agent-audit-npm-cache

npm publish --access public still requires npm ownership and authentication for @fullstackdegen/agent-audit.

Contributing

Focused issues and pull requests are welcome. Read CONTRIBUTING.md before changing the report contract, security policy, or MCP transport behavior.

License

MIT