@codyswann/lisa 1.28.0 → 1.29.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.
|
@@ -22,8 +22,4 @@ If no argument provided, search for plan files in the `plans/` directory and pre
|
|
|
22
22
|
|
|
23
23
|
## Agent Team Composition
|
|
24
24
|
|
|
25
|
-
Use the specialized agents listed in the
|
|
26
|
-
|
|
27
|
-
## Execution
|
|
28
|
-
|
|
29
|
-
Read the plan and begin implementation now.
|
|
25
|
+
Use the specialized agents listed in $ARGUMENTS and the @.claude/rules/plan.md rule (Implementation Team Guidance section). The **team lead** handles git operations (commits, pushes, PR management) -- teammates focus on their specialized work.
|
package/package.json
CHANGED
|
@@ -88,7 +88,7 @@
|
|
|
88
88
|
"@isaacs/brace-expansion": "^5.0.1"
|
|
89
89
|
},
|
|
90
90
|
"name": "@codyswann/lisa",
|
|
91
|
-
"version": "1.
|
|
91
|
+
"version": "1.29.0",
|
|
92
92
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
93
93
|
"main": "dist/index.js",
|
|
94
94
|
"bin": {
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
Run an OWASP ZAP baseline security scan locally using Docker.
|
|
2
|
-
|
|
3
|
-
Steps:
|
|
4
|
-
1. Check if Docker is installed and running: `docker info`
|
|
5
|
-
2. Check if `scripts/zap-baseline.sh` exists in the project
|
|
6
|
-
3. If it exists, run: `bash scripts/zap-baseline.sh`
|
|
7
|
-
4. If it does not exist, inform the user that this project does not have a ZAP baseline scan configured
|
|
8
|
-
5. After the scan completes, read `zap-report.html` (or `zap-report.md` for text) and summarize:
|
|
9
|
-
- Total number of alerts by risk level (High, Medium, Low, Informational)
|
|
10
|
-
- List each Medium+ finding with its rule ID, name, and recommended fix
|
|
11
|
-
- Categorize findings as "infrastructure-level" (fix at CDN/proxy) vs "application-level" (fix in code)
|
|
12
|
-
6. If the scan failed, explain what failed and suggest concrete remediation steps
|