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.
| Cache hits are counted, not only their bytes | 1 | [package] |
| 2 | name = "g1t-scan" | |
| 3 | version = "0.1.0" | |
| 4 | edition.workspace = true | |
| 5 | license.workspace = true | |
| 6 | description = "What g1t looks for in code: secrets, dependency lockfiles and OSV advisories, and git packs to find them in." | |
| 7 | ||
| 8 | [dependencies] | |
| 9 | serde.workspace = true | |
| 10 | serde_json.workspace = true | |
| 11 | miniz_oxide = "0.9" | |
| 12 | sha1 = "0.11" | |
| 13 | sha2 = "0.10" | |
| 14 | similar = "2" | |
| Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar | 15 | # Custom secret patterns: the regex crate's engines run in time linear in |
| 16 | # the text, with no backtracking, so no pattern can stall a push. | |
| 17 | regex = { version = "1.13", default-features = false, features = ["std", "perf", "unicode-perl", "unicode-case"] } |
This file's history is long; its oldest lines are credited to the oldest commit read.