@rafter-security/cli 0.9.0 → 0.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/commands/agent/components.js +4 -2
- package/dist/commands/agent/init.js +5 -4
- package/dist/commands/agent/instruction-block.js +21 -9
- package/dist/commands/backend/run.js +59 -1
- package/dist/commands/mcp/server.js +123 -0
- package/dist/commands/scan/index.js +2 -0
- package/dist/commands/sites/create.js +30 -0
- package/dist/commands/sites/errors.js +78 -0
- package/dist/commands/sites/get.js +30 -0
- package/dist/commands/sites/index.js +27 -0
- package/dist/commands/sites/list.js +39 -0
- package/dist/commands/sites/scan.js +54 -0
- package/dist/core/command-interceptor.js +28 -41
- package/dist/core/config-manager.js +9 -0
- package/dist/core/pattern-engine.js +33 -2
- package/dist/core/policy-loader.js +9 -0
- package/dist/core/risk-rules.js +408 -28
- package/dist/index.js +3 -0
- package/dist/scanners/secret-patterns.js +14 -0
- package/dist/utils/api.js +7 -0
- package/package.json +6 -2
- package/resources/rafter-security-skill.md +1 -1
- package/resources/skills/rafter/SKILL.md +18 -8
- package/resources/skills/rafter-code-review/SKILL.md +7 -1
- package/resources/skills/rafter-secure-design/SKILL.md +7 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: rafter-secure-design
|
|
3
|
-
description: "REQUIRED before writing code for any feature touching auth, payments, credentials, tokens, sessions, file upload, user data, or data deletion. Invoke it, record answers inline in the design doc or PR description, then write the code. Skipping this is how auth bypass, token leakage, and delete-the-wrong-record bugs ship. If the feature touches any of those surfaces and this hasn't run, the design is incomplete — do not proceed to implementation."
|
|
3
|
+
description: "REQUIRED before writing code for any feature touching auth, payments, credentials, tokens, sessions, file upload, user data, untrusted input, deserialization, network endpoints, or data deletion. Scope by that surface, not the task label — a research/experimental/local-only feature with none of it doesn't need this. Invoke it, record answers inline in the design doc or PR description, then write the code. Skipping this is how auth bypass, token leakage, and delete-the-wrong-record bugs ship. If the feature touches any of those surfaces and this hasn't run, the design is incomplete — do not proceed to implementation."
|
|
4
4
|
version: 0.1.0
|
|
5
5
|
allowed-tools: [Read, Glob, Grep]
|
|
6
6
|
---
|
|
@@ -11,6 +11,12 @@ A designer's skill, not a scanner. The goal is to catch the flaw in the whiteboa
|
|
|
11
11
|
|
|
12
12
|
> Pair with `rafter-code-review` (structured review *during* PR) and the `rafter` skill (automated detection of what slipped through). This skill is the earliest stage — prevention before the code exists.
|
|
13
13
|
|
|
14
|
+
## When this applies (and when it doesn't)
|
|
15
|
+
|
|
16
|
+
Engage this design walk when the feature you're about to build touches a real security surface: auth or access control, credentials / secrets / tokens / sessions, user or untrusted input, SQL or query construction, shell / `exec`, file paths or uploads, (de)serialization, crypto, network-facing endpoints or outbound fetchers, data deletion, or new dependencies.
|
|
17
|
+
|
|
18
|
+
If the thing you're designing has **none** of that — a research / experimental / local-only / throwaway piece such as a training script, analysis pipeline, plot, model-eval harness, notebook, or pure computation over trusted local data — a quick surface check is enough and you can proceed to implementation without the full walk. Judge by the surface, not by whether the work is called "research": a research feature that stores user data, handles a token, or opens a network endpoint is back on the engage list.
|
|
19
|
+
|
|
14
20
|
## How to use this skill
|
|
15
21
|
|
|
16
22
|
1. Identify what's being designed (below). If multiple apply, walk them in the order listed — `threat-modeling` last, as a capstone.
|