Four consumer tools: ScriptProbe, ListRun, MatchLine and BreachProbe

This issue carries consumer tools for checking package install scripts, directory submissions, resume evidence, and app security. The outputs are a verdict, a run sheet, a tailored PDF, and a security report.

This issue

These products turn narrow tasks into concrete results you can inspect.

ScriptProbe

ScriptProbe

ScriptProbe checks an npm package before you install it. It reads the tarball and lifecycle scripts as text, matches fixed patterns, and reports install scripts, network access, native builds, child processes, and publishing-account changes without executing the package. For a JavaScript developer or maintainer, the free check returns a verdict and the matching source text. You pay $15 once for a 30-day watch that rechecks a package.json or repository daily and emails changes.

ListRun

ListRun

ListRun is a directory-submission run sheet for a product owner who wants to see where a listing qualifies and what each submission requires. You answer what the product is, what it plugs into, and what it was built with, then ListRun shows the queue, the directories it will not attempt, and the order it reaches them. Each row carries a directory, submission method, qualification state, and note, with a receipt for every one. You pay $9 once for the Launch run or $19 once for the Full list.

MatchLine

MatchLine

	MatchLine checks a resume against a job posting, line by line. It reads every stated requirement, points to the resume line that proves it, and separates gaps with a line to add from gaps with nothing to build on. For a job seeker, the free check returns the reading and both documents without keeping an archive. You pay $5 for a tailored PDF.

BreachProbe

BreachProbe

BreachProbe checks whether a shipped app keeps one signed-in user's rows away from another. You paste an app URL and get a security score with checks for exposed keys, anonymous table access, headers, auth flows, and row-level isolation. For an app builder shipping user-owned data, the report uses two test users and compares table access rather than reading policy text. The result is a security report with findings, comparisons, and suggested fixes.

One issue a week, and one shipped product taken apart every month. What each product does, what it cost to build, what the pipeline behind it looks like, and what the numbers did, read off the repository and the live site, not written from memory. Join the list.