| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 6 | 0% |
| Commands | 0 | 0 | 1 | 0% |
| Section tags | 0 | 0 | 4 | 0% |
What each file covers
Sections
0 shared · 2 only in A · 6 only in B- − 📝 TASKS.md Update Rule (Severity: Warning)
- − Process:
- + Security Rules for Fasten
- + Input Validation
- + Build & Runtime Security
- + Reporting Vulnerabilities
- + User Best Practices
- + Hardening
Commands
0 shared · 0 only in A · 1 only in B- + zig build -Doptimize=ReleaseSafe
Section tags
0 shared · 0 only in A · 4 only in B- + build
- + code-style
- + security
- + do-not
Line diff
v1truv1us/fasten · .cursor/rules/task_tracking.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6# 📝 TASKS.md Update Rule (Severity: Warning)
7
8- ALWAYS update TASKS.md when completing any task or subtask
9- Mark items as ✅ Completed immediately after verification
10- Add verification notes for important milestones
11- Include test results and command examples for CLI/build features
12- Update the "Current Status" section to reflect the next target
13- Use specific markers: [✅] for complete, [🔄] for in progress, [🧪] for testing required
14- Include any bonus features or work that exceeded requirements
15- Update milestone progress when reaching key checkpoints
16
17## Process:
18- Complete a task/subtask
19- Test/verify it works
20- Immediately update TASKS.md with ✅ status
21- Add verification notes and test results
22- Update "Current Status" section
23- Commit the TASKS.md update along with the code changes
v1truv1us/fasten · .cursor/rules/security.mdc
@@ +3 @@
3globs:
4alwaysApply: true
5---
6# Security Rules for Fasten
7
8## Input Validation
9- Validate all file paths to prevent traversal.
10- Limit input file size and check permissions.
11- Validate and sanitize all input before processing.
12
13## Build & Runtime Security
14- Use only Zig stdlib; audit any external dependencies.
15- Reproducible, signed builds; secure distribution.
16- Strict memory management; bounds checking; safe allocations.
17- No sensitive info in error messages or logs.
18
19## Reporting Vulnerabilities
20- Do NOT report via public issues. Email security@fasten-bundler.dev with details.
21- Acknowledge within 48h, resolve critical issues within 30 days.
22
23## User Best Practices
24- Only process trusted files; verify file integrity.
25- Run in sandbox for untrusted input.
26- Keep system/tools updated; secure storage and access.
27
28## Hardening
29- Build with `zig build -Doptimize=ReleaseSafe`.
30- Use resource limits (ulimit) and minimal permissions for runtime.
31
@@ −3 +3 @@
33 globs:
44 alwaysApply: true
55 ---
6−# 📝 TASKS.md Update Rule (Severity: Warning)
6+# Security Rules for Fasten
77
8−- ALWAYS update TASKS.md when completing any task or subtask
9−- Mark items as ✅ Completed immediately after verification
10−- Add verification notes for important milestones
11−- Include test results and command examples for CLI/build features
12−- Update the "Current Status" section to reflect the next target
13−- Use specific markers: [✅] for complete, [🔄] for in progress, [🧪] for testing required
14−- Include any bonus features or work that exceeded requirements
15−- Update milestone progress when reaching key checkpoints
8+## Input Validation
9+- Validate all file paths to prevent traversal.
10+- Limit input file size and check permissions.
11+- Validate and sanitize all input before processing.
1612
17−## Process:
18−- Complete a task/subtask
19−- Test/verify it works
20−- Immediately update TASKS.md with ✅ status
21−- Add verification notes and test results
22−- Update "Current Status" section
23−- Commit the TASKS.md update along with the code changes
13+## Build & Runtime Security
14+- Use only Zig stdlib; audit any external dependencies.
15+- Reproducible, signed builds; secure distribution.
16+- Strict memory management; bounds checking; safe allocations.
17+- No sensitive info in error messages or logs.
18+
19+## Reporting Vulnerabilities
20+- Do NOT report via public issues. Email security@fasten-bundler.dev with details.
21+- Acknowledge within 48h, resolve critical issues within 30 days.
22+
23+## User Best Practices
24+- Only process trusted files; verify file integrity.
25+- Run in sandbox for untrusted input.
26+- Keep system/tools updated; secure storage and access.
27+
28+## Hardening
29+- Build with `zig build -Doptimize=ReleaseSafe`.
30+- Use resource limits (ulimit) and minimal permissions for runtime.
31+
