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

@l1ryx/audio-pipeline-auditor-unity

v0.1.1

Published

A CLI for auditing Unity audio pipelines and generating static HTML reports.

Readme

Audio Pipeline Auditor for Unity

A small TypeScript CLI for auditing Unity projects that use built-in audio or lightweight custom audio systems.

This project is a work in progress. Expect the scanner, report UI, and middleware coverage to evolve as more Unity project shapes are tested.

Audio Pipeline Auditor report screenshot

Install it with npm, then run the scanner against a Unity project path.

What It Checks

  • Scan Unity project folders for audio files and Unity text assets.
  • Detect oversized audio, unreferenced clips, missing AudioSource clips, unresolved clip GUIDs, missing mixer routing, Play On Awake, and suspicious AudioSource volume.
  • Detect audio pipeline architecture: serialized AudioSource components, runtime-created Unity audio, ScriptableObject audio definitions, and Wwise artifacts.
  • Summarize obvious Wwise and FMOD script calls, including common API names and first string event arguments.
  • Build a structured JSON report.
  • Render a static React-powered HTML report.
  • Return CI-friendly exit codes when findings reach a configured severity.

Quick Start on a Unity Project

Install the CLI:

npm install -g @l1ryx/audio-pipeline-auditor-unity

Scan a Unity project:

audio-audit scan /path/to/MyUnityProject --out /path/to/MyUnityProject/audio-audit-report

Then open:

/path/to/MyUnityProject/audio-audit-report/index.html

Do not run npm install inside the Unity project. The Unity project is only the scan target.

If you want a config file:

audio-audit init

Build From Source

You can also clone and build the auditor locally:

git clone https://github.com/l1ryx/audio-pipeline-auditor.git
cd audio-pipeline-auditor
npm install
npm run build
node dist/cli.js scan /path/to/MyUnityProject --out /path/to/MyUnityProject/audio-audit-report

The generated report includes schemaVersion: "0.1.0" in report.json so future report viewers can handle report shape changes deliberately.

Reports

Audio Pipeline Auditor scans your Unity project locally or in CI. It does not require uploading your Unity project to a website.

Each scan writes a static report folder:

audio-audit-report/
  index.html
  report.json

Open index.html in a browser to view the report. You can also upload the report folder as a CI artifact or host the generated files on any static file host.

Limitations

  • Unity assets must be serialized as text for scene, prefab, and asset scanning to be useful.
  • Audio metadata depends on what music-metadata can read from the discovered files.
  • Wwise and FMOD support is intentionally lightweight: the scanner summarizes obvious script calls, common component names, and simple artifacts, but it does not parse full Wwise projects, FMOD Studio projects, or bank contents.
  • The report is a static snapshot. It does not watch project files or upload project contents.