github.com/go-openapi/codescan v0.36.5
.env configuration fileAccount collection path fragment
SHA-256d7cba07460457f5c1bfc57db2230475a2f1120c4b87fb528c74c64802fa8b5bd
Evidence
1# CLAUDE.md
2
3This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
4
5## Project Overview
6
7Go source code scanner that parses Go packages and produces [Swagger 2.0](https://swagger.io/specification/v2/)
8(OpenAPI 2.0) specifications. It r …
12:7… aintainers documentation][maintainers-doc-site] for CI/CD, release process, and repo structure details.
13
14[maintainers-doc-site]: https://go-openapi.github.io/doc-site/maintainers/index.html
15
16## Package layout
17
18Single Go module `github.com/go-openapi/codescan`. Public API lives at the root; implementation is
19split under `internal/` into three layers: **scanner** (package/AST ing …
38:10… go` | `TypeIndex` — node classification (meta/route/operation/model/parameters/response) |
39| `declaration.go` | `EntityDecl` — wraps a type/value declaration with its enclosing file/package |
40| `written_rhs.go` | …
166:35… by CodeQL analysis)
167
168### Undue secret exposure
169
170**NEVER** use `secrets[inputs.name]` — always use explicit secret parameters.
171
172> Using keyed access to secrets forces the runner to expose ALL secrets to the job, which causes a security risk
173> (caught and reported by CodeQL security analysis).
174
175```yaml
176# ❌ SECURITY VULNERABI …
⋯13 lines
14```
15
16**Mono-repos (with `go.work`):**
17
18```sh
⋯5 lines
24```
25
26Note: in mono-repos, plain `go test ./...` only tests the root module.
27The `work` pattern expands to all modules listed in `go.work`.
28
29CI runs tests on `{ubuntu, macos, windows} x {stable, oldstable}` with `-race` via `gotestsum`.
30
31## Fuzz tests
32
33```sh
34# List all fuzz targets
35go test -list Fuzz ./...
36
37# Run a specific target (go test -fuzz cannot span multiple packages)
38go test -fuzz=Fuzz -run='FuzzTargetName$' -fuzztime=1m30s ./package
39```
40
41Fuzz corpus lives in `testdata/fuzz/` within each package. CI runs each fuzz target for 1m30s
42with a 5m minimize timeout.
43
⋯4 lines
Showing the top 5 files — 4 more files (20 regions) not shown.
No evidence locations were recorded for this file. Raw result