| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 6 | 0% |
| Commands | 0 | 0 | 1 | 0% |
| Section tags | 1 | 1 | 3 | 20% |
What each file covers
Sections
0 shared · 6 only in A · 6 only in B- − Performance Rules for Fasten
- − Targets
- − Benchmarking
- − Memory
- − Optimization
- − Monitoring
- + 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
1 shared · 1 only in A · 3 only in B- − performance
- + build
- + code-style
- + security
- do-not
Line diff
v1truv1us/fasten · .cursor/rules/performance.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6# Performance Rules for Fasten
7
8## Targets
9- Small: <100ms, <10MB; Medium: <500ms, <50MB; Large: <2s, <200MB; XL: <10s, <500MB.
10- Lexer: >1MB/s; Parser: >500KB/s; Optimizer: >2MB/s; Codegen: >5MB/s.
11- Cold start <50ms; base memory <5MB.
12
13## Benchmarking
14- Use provided benchmark framework; warmup, multiple iterations, throughput checks.
15- Assert performance targets in tests; fail on regression >10%.
16
17## Memory
18- Use ArenaAllocator for temp data; Pool for frequent allocations.
19- Profile memory; zero tolerance for leaks; peak usage <2x input size.
20
21## Optimization
22- Minimize allocations in hot paths; use stack allocation when possible.
23- Profile before optimizing; document all optimizations.
24- Use efficient data structures (interning, compact AST).
25
26## Monitoring
27- Collect and log metrics (time, memory, compression ratio).
28- Alert on slow bundling, high memory, poor compression.
29- Run performance and memory tests in CI.
30
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−# Performance Rules for Fasten
6+# Security Rules for Fasten
77
8−## Targets
9−- Small: <100ms, <10MB; Medium: <500ms, <50MB; Large: <2s, <200MB; XL: <10s, <500MB.
10−- Lexer: >1MB/s; Parser: >500KB/s; Optimizer: >2MB/s; Codegen: >5MB/s.
11−- Cold start <50ms; base memory <5MB.
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.
1212
13−## Benchmarking
14−- Use provided benchmark framework; warmup, multiple iterations, throughput checks.
15−- Assert performance targets in tests; fail on regression >10%.
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.
1618
17−## Memory
18−- Use ArenaAllocator for temp data; Pool for frequent allocations.
19−- Profile memory; zero tolerance for leaks; peak usage <2x input size.
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.
2022
21−## Optimization
22−- Minimize allocations in hot paths; use stack allocation when possible.
23−- Profile before optimizing; document all optimizations.
24−- Use efficient data structures (interning, compact AST).
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.
2527
26−## Monitoring
27−- Collect and log metrics (time, memory, compression ratio).
28−- Alert on slow bundling, high memory, poor compression.
29−- Run performance and memory tests in CI.
28+## Hardening
29+- Build with `zig build -Doptimize=ReleaseSafe`.
30+- Use resource limits (ulimit) and minimal permissions for runtime.
3031
