Web QA
static-preflight
A broken link checker and launch checklist for a static site build: SEO basics, links and assets, redirects, share cards, icons, JSON-LD and old-URL coverage.
A fetch-only security headers checker and website scanner: about a hundred security, SEO and speed checks, with a score and a fix hint for each finding.
npm install siteprobesiteprobe is a security headers checker you run from the command line or from code. It fetches a page and the few files around it (robots.txt, sitemap.xml, security.txt and a sample of its CSS and JS), runs about a hundred security, SEO and speed checks, and returns a score, a grade and findings with evidence and a fix hint for each.
It has no dependencies and no headless browser, so it runs anywhere fetch does: Node 20+, Cloudflare Workers, Deno and Bun. Lighthouse needs a headless Chrome and measures a rendered page, and Mozilla HTTP Observatory only looks at security headers. siteprobe reads the HTML and headers the server sends and covers security, SEO and speed in one pass.
It powers the free security scanner at developerlook.com.
npx siteprobe https://example.comsiteprobe https://example.com
security 53/100 F 2 high, 4 medium, 4 low, 4 info, 13 passed
HIGH (2)
[security] Content-Security-Policy header missing (missing-csp)
Fix: Add a Content-Security-Policy header. Minimum: Content-Security-Policy: default-src 'self'
[security] HSTS (HTTP Strict-Transport-Security) not configured (missing-hsts)
Fix: Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preloadnpx siteprobe https://staging.example.com --fail-on mediumimport { scanSecurity } from 'siteprobe';
const result = await scanSecurity('https://example.com');
console.log(result.score, result.grade); // 53 'F'
for (const finding of result.findings) {
console.log(finding.severity, finding.id, finding.remediation);
}import { scan } from 'siteprobe';
const report = await scan('https://example.com', { checks: ['security', 'seo'], timeoutMs: 8000 });
console.log(report.results.security?.score, report.results.seo?.metrics.word_count);
console.log(report.errors); // a scan that fails lands here and the others still runimport { scanSecurity } from 'siteprobe';
export default {
async fetch(request: Request): Promise<Response> {
const url = new URL(request.url).searchParams.get('url') ?? '';
const result = await scanSecurity(url, { ownHost: new URL(request.url).hostname });
return Response.json(result);
},
};siteprobe <url> [--only security,seo,speed] [--json] [--fail-on high|medium|low|none] [--no-active] [--timeout ms]Run npx siteprobe https://example.com --only security. It prints a score, a grade and each finding with the header to add or change. Add --json for the full report, or --fail-on medium to make the command exit 1 in CI.
It checks both as part of the security scan. For Content-Security-Policy it reports a missing header, unsafe-inline and unsafe-eval. For HSTS it reports a missing header, a short max-age and no includeSubDomains. Each finding has a fix hint. It does not check TLS certificates, DNS or email security.
Lighthouse loads the page in a headless Chrome and measures the rendered result. siteprobe uses only fetch: it reads the headers and HTML the server sends, so it runs in places a browser cannot, such as a Cloudflare Worker, and it covers security headers that Lighthouse does not.
Scan only sites you own or are allowed to test. By default siteprobe also requests well-known sensitive paths such as /.env and /admin, which can trip alarms. Use --no-active to send only ordinary GET requests.
Yes. The CLI exits 1 when a finding is at or above the --fail-on level (high by default), so npx siteprobe https://staging.example.com --fail-on medium fails the build on anything medium or worse. Staging servers on a private network need --allow-private.
Web QA
A broken link checker and launch checklist for a static site build: SEO basics, links and assets, redirects, share cards, icons, JSON-LD and old-URL coverage.
Web QA
Responsive design testing that measures the layout at every viewport width: overflow, clipping, inconsistent insets and radii, low-resolution images and layout shift.
Web QA
Find redirect chains, loops and clashes in a whole rule set, then flatten every chain to one hop before you ship.
Author
Saimul Islam is a Forward Deployed Engineer and Solutions Architect. Several of these packages run in production on DeveloperLook, the Bundlewise CRM and Sitessa.