Skip to content
29 linesCodeBlameRaw

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 API1[package]
2name = "g1t-security"
3version = "0.1.0"
4edition.workspace = true
5license.workspace = true
6description = "Secret scanning, push protection decisions, vulnerable dependencies and the upgrades that fix them."
7
8[lib]
9crate-type = ["cdylib"]
10
11[dependencies]
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar12g1t-actions.workspace = true
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API13g1t-contracts.workspace = true
14g1t-kit.workspace = true
15g1t-scan.workspace = true
16serde.workspace = true
17serde_json.workspace = true
Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily18serde_yaml = "0.9"
Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar19# The dependency update file is read with its lines, so each problem says where it is.
20yaml-rust2 = { version = "0.13", default-features = false }
21toml = "0.8"
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API22worker.workspace = true
23futures-util = { version = "0.3", default-features = false, features = ["alloc"] }
24getrandom = { 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 workflow25
26# wasm-opt at -O1: about the same gzipped size as -O in a tenth of the
The docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.27# time.
Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow28[package.metadata.wasm-pack.profile.release]
29wasm-opt = ["-O1"]