g1t/services/security/Cargo.toml
Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API | 1 | [package] |
| 2 | name = "g1t-security" | |
| 3 | version = "0.1.0" | |
| 4 | edition.workspace = true | |
| 5 | license.workspace = true | |
| 6 | description = "Secret scanning, push protection decisions, vulnerable dependencies and the upgrades that fix them." | |
| 7 | ||
| 8 | [lib] | |
| 9 | crate-type = ["cdylib"] | |
| 10 | ||
| 11 | [dependencies] | |
| 12 | g1t-contracts.workspace = true | |
| 13 | g1t-kit.workspace = true | |
| 14 | g1t-scan.workspace = true | |
| 15 | serde.workspace = true | |
| 16 | serde_json.workspace = true | |
| Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily | 17 | serde_yaml = "0.9" |
| Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API | 18 | worker.workspace = true |
| 19 | futures-util = { version = "0.3", default-features = false, features = ["alloc"] } | |
| 20 | getrandom = { version = "0.2", features = ["js"] } | |
| Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow | 21 | |
| 22 | # wasm-opt at -O1: about the same gzipped size as -O in a tenth of the | |
| 23 | # time (docs/DEPLOYING.md, "Build speed"). | |
| 24 | [package.metadata.wasm-pack.profile.release] | |
| 25 | wasm-opt = ["-O1"] |