gatling-build-tools — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited gatling-build-tools (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Inspect the project root and identify the build tool by looking for these files, in this order:
pom.xmlpackage.jsonbuild.gradle, or build.gradle.ktsbuild.sbtOnce the build tool is identified, read the corresponding file and follow its instructions:
These checks apply regardless of build tools:
.gatling/package.conf exists and is not empty.If missing or empty, help the user create it using the Configuration as Code skill.
GATLING_ENTERPRISE_API_TOKEN is set.Follow the instructions from the file loaded in Step 2 for:
The output logs package and test IDs. Suggest updating .gatling/package.conf with these IDs for consistent future deployments.
Ask the user if they want to start the test on Gatling Enterprise. If so, follow the instructions from the file loaded in Step 2 for running the start command.
If the build tool deploy/start or any MCP tool call fails, check authentication first:
GATLING_ENTERPRISE_API_TOKEN is set in the environment.direnv, and offer to create a .envrc file.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.