Repository navigation
0.14.0 - npm package
Packages
- The CLI and the engine are published to npm as one package,
pandapaylens: thepandapaylensbinary, and a library entry withanalyze(text, options?), the engine, every adapter, the default rules and the report helpers. JavaScript is bundled (no runtime dependencies) and type declarations resolve on their own. CI installs the packed tarball into an empty project and checks the binary and a typed import; a workflow publishes to npm with provenance when a GitHub release is published.
Documentation
- The getting-started page, README and roadmap use the npm package (
npx pandapaylens,import { analyze } from "pandapaylens").
Maintenance
- A monthly workflow requests every official documentation link cited by adapters, catalogs, manifests and rules, and fails when one returns 404 or 410, redirects to a "page not found" page or names a host that does not resolve (
node scripts/check-doc-links.mjs).
Install: npx pandapaylens analyze events.json or npm install pandapaylens.