-
Notifications
You must be signed in to change notification settings - Fork 0
reference dependencies
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
QA Scribe uses a Rust workspace for core and desktop backend code, plus a Bun-managed React frontend.
| Dependency | Used for |
|---|---|
tauri, tauri-build, tauri-specta
|
Desktop shell, build integration, command bindings. |
rusqlite |
Local SQLite storage with bundled SQLite. |
serde, serde_json
|
DTO serialization. |
specta, specta-typescript
|
Type export to TypeScript. |
chrono |
Timestamps. |
uuid |
IDs. |
sha2, base64
|
Attachment hashing and data URLs. |
thiserror |
Core error type. |
Versions are declared in Cargo.toml and locked in Cargo.lock.
Frontend dependencies are declared in frontend/package.json and locked in frontend/bun.lock. The renderer uses React, TypeScript, Vite, Vitest/jsdom, TipTap editor packages, and styling through CSS files under frontend/src/styles.
package.json defines bun run frontend:audit for high-severity frontend dependency audit. Cargo dependencies are checked by normal compile, clippy, and test commands in bun run verify.
See Tooling for command details.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies