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

@codacy/tools-prospector-1

v0.1.3

Published

Prospector tool adapter for Codacy analysis

Readme

@codacy/tools-prospector-1

Table of Contents


Overview

Prospector is a meta-tool for Python static analysis that orchestrates multiple linters (pylint, pyflakes, pycodestyle, mccabe, dodgy, pydocstyle) and optional tools (bandit, mypy, vulture, pyroma, pyright), running them against the same codebase and merging their output with cross-tool deduplication ("blending").

| Property | Value | | ------------- | ---------------------------------------------- | | Tool ID | Prospector | | Codacy UUID | 25673894-eac1-4941-87a6-81f1abd5c321 | | Strategy | CLI (child process via spawnTool, Python venv) | | Languages | Python | | File patterns | **/*.py |

Updating patterns

# Re-fetch pattern metadata from the Codacy API
pnpm prefetch

# Commit the result
git add src/patterns.json

Updating the Prospector version

  1. Update preferredVersion and PIP_PACKAGES version pin in src/adapter.ts
  2. Update pinned pylint/mypy versions if the Codacy wrapper changes them
  3. Run pnpm prefetch to check for new/removed sub-tools
  4. Run pnpm test to verify compatibility
  5. If the major version changes, create a new adapter package (prospector-2/)

Development

pnpm build    # Build with tsup
pnpm test     # Run tests

To run integration tests locally, install prospector:

pip install prospector[with_everything]==1.18.0

Notes for maintainers

  • Meta-tool architecture: Prospector wraps multiple sub-tools. Patterns are tool-level (e.g. Prospector_pylint), not per-rule. The source field in Prospector's JSON output identifies which sub-tool produced each message.

  • Blending: Prospector deduplicates equivalent messages across tools (e.g. pylint's unused-import and pyflakes' F401). The adapter runs with blending enabled (default) to match the existing Codacy wrapper behavior.

  • Denylist codes: Messages with codes failure, django-not-configured, and import-error are filtered out, matching the existing wrapper.

  • File chunking: Files are processed in chunks of 50 per invocation to avoid command-line length limits.

  • Framework detection: The adapter uses --no-autodetect for deterministic behavior. Django/Flask/Celery plugins are not auto-loaded.

  • Overlap with standalone adapters: Since Prospector wraps pylint, pyflakes, etc., there is overlap with standalone adapters (e.g. pylint-3, bandit-1). Prospector's sub-tool versions may differ from standalone adapter versions. Users should choose one approach per tool, not both.

  • Column numbers: Some sub-tools (mccabe, dodgy) report null for columns. Since Issue.column is required, the adapter defaults to column 1 when the sub-tool does not report a column offset.