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

promptlint-cli

v1.3.0

Published

Static analysis for LLM prompts — catch cost waste, quality issues, and injection risks

Readme

promptlint

Static analysis for LLM prompts — catch token waste, quality issues, and injection risks before they reach production.

npm version License

Install

npm install -g promptlint
# or use without installing
npx promptlint --text "your prompt here"

Usage

# Lint a file
promptlint prompt.txt

# Lint inline text
promptlint --text "Please kindly write me some code"

# Pipe from stdin
cat prompt.txt | promptlint

# Lint multiple files / globs
promptlint prompts/**/*.txt

# Apply auto-fixes
promptlint --fix prompt.txt

# JSON output (for CI integration)
promptlint --format json prompt.txt

# Show token savings dashboard
promptlint --show-dashboard prompt.txt

# CI mode — exit 1 on warnings
promptlint --fail-level warn prompt.txt

Rules

| ID | Category | Severity | Auto-fix | |----|----------|----------|----------| | cost | Cost | INFO | — | | cost-limit | Cost | WARN | — | | prompt-injection | Security | CRITICAL | yes | | structure-sections | Structure | WARN | yes | | clarity-vague-terms | Quality | WARN | — | | specificity-examples | Quality | INFO | — | | specificity-constraints | Quality | INFO | — | | politeness-bloat | Quality | WARN | yes | | verbosity-sentence-length | Quality | INFO | — | | verbosity-redundancy | Quality | INFO | yes | | actionability-weak-verbs | Quality | INFO | — | | consistency-terminology | Quality | INFO | — | | completeness-edge-cases | Quality | INFO | — |

# List all rules
promptlint --list-rules

# Explain a rule
promptlint --explain prompt-injection

Configuration

Generate a starter config:

promptlint --init

This creates a .promptlintrc (YAML) in your current directory:

model: gpt-4o
token_limit: 800
cost_per_1k_tokens: 0.005
calls_per_day: 10000

rules:
  prompt_injection:
    enabled: true
    patterns:
      - ignore previous instructions
  politeness_bloat:
    enabled: true
    words: [please, kindly, thank you]

fix:
  enabled: true
  politeness_bloat: true
  verbosity_redundancy: true

Disable rules inline

Please write some code  # promptlint-disable politeness-bloat
Some vague stuff        # promptlint-disable

Programmatic API

import { analyze, applyFixes, loadConfig } from "promptlint";

const config = loadConfig(); // reads .promptlintrc
const findings = analyze("Please kindly write some code", config);
const fixed = applyFixes("Please kindly write some code", config);

console.log(findings);
// [{ level: 'WARN', rule: 'politeness-bloat', message: '...' }]

Exit codes

| Code | Meaning | |------|---------| | 0 | No issues (or below fail-level) | | 1 | Warnings found (with --fail-level warn) | | 2 | Critical issues found |

Links

License

Apache-2.0