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

@groma/scanner-php

v0.1.0

Published

PHP source declarations and operations without project dependencies.

Downloads

85

Readme

PHP scanner

The PHP scanner reads tracked and unignored .php files, including PHP embedded in HTML. It does not require Composer, PHP, WordPress, project dependencies, or application execution. Discovery matches PHP source directly, even without a package manifest.

bun plugins/scanners/php/build.ts

From the project being scanned:

groma scanner add /absolute/path/to/groma/plugins/scanners/php/dist/package
groma scan

The package bundles php-parser 3.7.0, a JavaScript parser configured for PHP syntax through 8.4. It includes the parser license and needs no installation scripts or downloads while scanning. This is source syntax analysis, not a PHP runtime compatibility check. Newer syntax outside the bundled parser is unsupported; parser errors fail the observation rather than publish partial evidence.

Evidence

The scanner reports one repository source root, exact PHP paths, named functions, classes, interfaces, traits, enums, and methods. Implemented functions, methods, closures, and arrow functions produce operation evidence with UTF-16 source offsets. Calls and constructions within these operations remain unresolved. Top-level executable statements are inventoried as part of their source file; they do not create artificial functions.

The repository source root is initial placement evidence, not a claim that every PHP file belongs to one C4 runtime boundary. Core owns architecture identity and curation. There is no Composer autoload resolution, include execution, WordPress hook matching, dependency resolution, or HTTP relationship inference. An import or include does not associate files into a component. Ordinary OKF Code links expose file ownership without adding a new architecture level or stored graph.

PHP edits and new files use the shared scanner watcher. Repeated scans preserve one physical owner and authored architecture. Shared Git boundaries omit ignored files and dependency/build output directories. Core applies configured source exclusions. Test source is otherwise treated like other PHP source; projects can exclude it explicitly.

Validation

Independent fixtures cover declarations, mixed PHP/HTML, nested function ownership, exact source locations, unresolved calls, invalid syntax, discovery without Composer, repeat scans and live source edits. The fresh-checkout package check removes language tools from PATH and blocks JavaScript network access. See local qualification for the Call for Papers example.