Projects

Projects let you group related audits together. Each project stores its crawl history, cached pages, and audit results in a dedicated folder.

How projects work

When you run an audit, squirrelscan creates a project folder to store all data:

By default, the project name is derived from the domain you’re auditing. You can override this to:

• Group multiple domains under one project
• Track the same website across environments (dev, staging, prod)
• Keep separate audit histories for different purposes

Setting the project name

Via config file

Add a name field to the [project] section in squirrel.toml:

[project]
name = "my-website"
domains = ["example.com", "www.example.com"]

Via command line

Use the --project-name (or -n) flag to override the project name for a single audit:

squirrel audit https://example.com --project-name my-website

This is useful for:

• One-off audits you want to keep separate
• Testing without affecting your main project history
• CI/CD pipelines where config files aren’t available

Auditing local development sites

You can audit localhost and other local development servers:

# Audit your local dev server
squirrel audit http://localhost:3000

# Audit with a custom project name
squirrel audit http://localhost:3000 -n my-app-dev

This is useful for:

• Pre-deploy checks - Catch issues before they go live
• Development workflow - Fix SEO and accessibility issues as you build
• CI/CD integration - Audit preview deployments automatically

Separating dev and production audits

Use different project names to keep development and production audits separate:

# For local development
[project]
name = "my-app-dev"

# For production (override via CLI)
squirrel audit https://my-app.com -n my-app-prod

Or use environment-specific config files:

• squirrel.toml - Development settings
• squirrel.prod.toml - Production settings

Viewing project data

Project data is stored in ~/.squirrel/projects/<project-name>/:

You can inspect the database directly or use the CLI:

# List recent audits for a project
squirrel report --list

# View a specific audit
squirrel report <audit-id>

Use cases

Multi-environment tracking

Track the same site across environments:

# Development
squirrel audit http://localhost:3000 -n mysite-dev

# Staging
squirrel audit https://staging.mysite.com -n mysite-staging

# Production
squirrel audit https://mysite.com -n mysite-prod

Multi-domain projects

Group related domains under one project:

[project]
name = "company-sites"
domains = ["company.com", "blog.company.com", "docs.company.com"]

Timestamped snapshots

Create point-in-time snapshots for comparison:

squirrel audit https://example.com -n example-2024-01
squirrel audit https://example.com -n example-2024-02

Project storage location

All projects are stored in:

~/.squirrel/projects/

Each project gets its own subdirectory with a SQLite database containing all crawl and audit data.