actually-lsp-ignore — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited actually-lsp-ignore (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.
Parse args:
rust | typescript | ruby as an arg ignores that ecosystem directly..claude/actually-lsp.json in the current project root, present the detected ecosystems, and ask the user which to ignore.Update the project state file at .claude/actually-lsp.json: set .ecosystems.<ecosystem>.dismissed to true. If the file doesn't exist, create it with version 1 schema:
{
"version": 1,
"ecosystems": {
"<ecosystem>": {
"state": "dismissed",
"dismissed": true,
"last_check_at": null,
"last_marker_mtime": null,
"last_plugin_list_hash": null,
"last_error": null
}
}
}If the file exists, preserve all other fields and only flip dismissed.
The internal state value stays dismissed (that's the state-machine name from CONTEXT.md); only the user-facing skill name is ignore.
Output a one-line confirmation per ignored ecosystem:
Ignoring <ecosystem> for this project. To re-enable, manually edit .claude/actually-lsp.json and set dismissed back to false. (A re-enable command is a future extension.)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.