TypeScript Strict Mode — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited TypeScript Strict Mode (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.
Strict TypeScript or nothing. Every any is a bug waiting to happen.
any — use unknown and narrow, or define the typeas SomeType — use type guards or narrowing instead!.property — handle null/undefined explicitly@ts-ignore — fix the type error, don't suppress itany in function parametersunknown over any for truly unknown data (then narrow)satisfies over as for type assertionsconst assertions for literal typesnever checks// Type guard
function isUser(x: unknown): x is User {
return typeof x === 'object' && x !== null && 'id' in x
}
// Exhaustive switch
function handle(action: Action): never {
switch (action.type) {
case 'A': return handleA(action)
case 'B': return handleB(action)
default: const _exhaustive: never = action; throw new Error()
}
}tsconfig.json must have: "strict": true — this enables all strict checks.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.