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

zap-clean-report

v0.1.1

Published

Generate clean, non-technical HTML reports from OWASP ZAP JSON output

Readme

zap-clean-report

Generate clean, non-technical HTML security reports from OWASP ZAP JSON output.

Built for teams who need to share scan results with developers, managers, and stakeholders who are not security specialists. Findings are written in plain English, grouped by severity, and the output is a single self-contained HTML file with no external dependencies.

Features

  • Single self-contained HTML file (no CDN, no internet required to open)
  • Plain English descriptions for common vulnerability types
  • Findings grouped and filterable by risk level (High, Medium, Low, Informational)
  • OWASP Top 10 category badges per finding
  • CWE reference badges with clickable links
  • Systemic finding detection
  • Collapsible finding details with affected URL list
  • Print-ready layout with all sections expanded automatically
  • Auto-generated filename based on target hostname and UTC timestamp
  • Zero runtime dependencies

Install

npm install -g zap-clean-report

Or run without installing:

npx zap-clean-report zap-output.json

Usage

zap-clean-report <input.json> [options]

Options

| Option | Description | |---|---| | --output, -o <file> | Output file path (overrides auto-generated name) | | --title <text> | Report title (default: Security Scan Report) | | --help, -h | Show help |

Examples

# Basic usage - auto-generates filename
zap-clean-report zap-output.json

# Custom output path
zap-clean-report zap-output.json --output report.html

# Custom title (appears in the report header)
zap-clean-report zap-output.json --title "My App - Sprint 22"

Auto-generated filename format

<hostname>-<UTC timestamp>-security-report.html

Example: app.example.com-20260504164752-security-report.html

Programmatic usage

const { generateReport } = require('zap-clean-report');
const fs = require('fs');

const raw = JSON.parse(fs.readFileSync('zap-output.json', 'utf8'));
const html = generateReport(raw, { title: 'My App - Security Scan' });
fs.writeFileSync('report.html', html);

Input format

Accepts the standard JSON export from OWASP ZAP. To generate it:

  1. Run your ZAP scan
  2. Go to Report > Generate Report and select JSON format, or use the ZAP CLI with --format json

Sample JSON files for testing are available in the examples/ folder.

Requirements

Node.js 16 or later.

License

MIT