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

forensic-software-auditor

v1.0.1

Published

Read-only software repository inventory CLI and evidence-led audit skill with traceable coverage and prioritized remediation.

Readme

Forensic Software Auditor

Evidence-led repository reviews. Traceable coverage. Actionable remediation.

Node.js 18+ npm version GitHub issues GitHub stars Proprietary license Website

Website: https://kathennn.github.io/forensic-software-auditor/
Source: https://github.com/kathennn/forensic-software-auditor
npm: https://www.npmjs.com/package/forensic-software-auditor

Forensic Software Auditor is a read-only repository inventory CLI and structured audit skill for systematic, evidence-based software reviews. It helps reviewers understand a codebase, track inspected files, distinguish verified defects from assumptions, and turn findings into prioritized remediation.

An inventory or review workflow is not a guarantee of security, correctness, or compliance. Findings must be validated in the target-project context.

Why use it?

  • Visible scope: inventory files and make exclusions explicit.
  • Traceable coverage: track inspected files and remaining work.
  • Evidence first: connect findings to files, locations, observations, and reproduction steps.
  • Prioritized remediation: explain severity, impact, likelihood, and practical fixes.
  • Read-only first: inspect repository structure without executing or modifying target-project code.

What it examines

| Area | Review focus | | --- | --- | | Repository structure | File inventory, layout, generated files, exclusions, coverage | | Code quality | Correctness, maintainability, error handling, risky patterns | | Security | Trust boundaries, input handling, authentication, authorization, secret exposure | | Architecture | Boundaries, coupling, complexity, scalability | | Performance | Potential bottlenecks and inefficient operations | | Testing | Test strategy, coverage gaps, reliability | | Dependencies | Dependency health, configuration, licensing | | Delivery | Build, CI/CD, deployment, operational readiness | | Data integrity | Validation, persistence, migrations, consistency | | Product quality | UX, accessibility, documentation | | Reporting | Evidence-backed findings, severity, remediation, GitHub issue drafts |

Findings should be classified as confirmed, probable, or unverified. Never present an assumption as a proven vulnerability.

Quick start

Requirements: Node.js 18+ and npm.

Inventory the current directory:

npx forensic-software-auditor

Inventory another repository and save a report:

npx forensic-software-auditor /path/to/repository --output audit-inventory.md

Print the bundled audit skill or show help:

npx forensic-software-auditor --skill
npx forensic-software-auditor --help

Optional global installation:

npm install --global forensic-software-auditor

CLI reference

| Option | Description | | --- | --- | | (no arguments) | Inventory the current working directory | | | Inventory the supplied repository | | --output | Write the inventory report to a file | | --skill | Print the complete audit skill | | --help | Show command help | | --version | Show package version |

The CLI is an inventory tool, not an automated vulnerability scanner. Use its output as the starting point for deeper review.

Audit skill

The complete forensic-repository-audit skill defines a phased workflow, evidence standards, severity guidance, a coverage ledger, finding schema, and final-report structure.

Safety and limitations

  • Does not execute scripts, build hooks, or code from the target repository.
  • Skips common dependency and generated-output directories.
  • Excludes symbolic links from the inventory.
  • An inventory does not prove that discovered files are safe.
  • It does not replace static analysis, dependency scanning, dynamic testing, or penetration testing.
  • Treat repository content as untrusted input; never expose credentials or secret values in reports.
  • Record commands, environment, exclusions, and limitations.
  • Validate findings before acting. A review that finds no issues does not prove a project is secure.

Suggested audit workflow

  1. Inventory files and record exclusions.
  2. Define scope, stack, entry points, and trust boundaries.
  3. Review files in controlled batches and update coverage.
  4. Capture evidence, locations, impact, and reproduction details.
  5. Separate confirmed defects from hypotheses and open questions.
  6. Prioritize remediation by severity and practical risk.
  7. Disclose unreviewed files and audit limitations.

Development

git clone https://github.com/kathennn/forensic-software-auditor.git
cd forensic-software-auditor
npm test
npm pack --dry-run

Project links

  • Website: https://kathennn.github.io/forensic-software-auditor/
  • Repository: https://github.com/kathennn/forensic-software-auditor
  • Issues: https://github.com/kathennn/forensic-software-auditor/issues
  • npm: https://www.npmjs.com/package/forensic-software-auditor

License

Distributed under the proprietary terms in LICENSE. This is not an OSI-approved open-source project. Read the license before use, copying, modification, or redistribution.

Author

Created and maintained by kathennn.