- Go 92.2%
- Ruby 3%
- Nix 1.7%
- HTML 1.4%
- YAML 1%
- Other 0.7%
ae4debbe43Hi, and thank you for GoReleaser. This adds a machine-readable `/.well-known/security.txt` (RFC 9116) to the site's `www/static/` dir, so it serves at `https://goreleaser.com/.well-known/security.txt` (currently 404). It points automated tooling at the disclosure channel your `SECURITY.md` already documents (GitHub Security Advisories): ``` Contact: https://github.com/goreleaser/goreleaser/security/advisories/new Policy: https://github.com/goreleaser/goreleaser/blob/main/SECURITY.md Preferred-Languages: en Canonical: https://goreleaser.com/.well-known/security.txt Expires: 2027-01-01T00:00:00.000Z ``` I verified the `www/static/` passthrough serves at the site root (e.g. `goreleaser.com/favicon.ico` and `/card.png` both return 200), so this file will be served at the well-known path. RFC 9116 recommends refreshing `Expires` at least annually — feel free to adjust. Per your AI usage guidelines: AI assistance was used to identify this and draft the file (the commit carries an `Assisted-by` marker). I fully reviewed the change and verified the live 404, the serving passthrough, and the SECURITY.md channel myself. |
||
|---|---|---|
| .copilot/skills/authoring-docs | ||
| .github | ||
| cmd | ||
| internal | ||
| pkg | ||
| scripts | ||
| testdata/TestVersion | ||
| www | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yaml | ||
| .goreleaser.yaml | ||
| .grype.yaml | ||
| .mailmap | ||
| .svu.yml | ||
| art.txt | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| EULA.md | ||
| go.mod | ||
| go.sum | ||
| INCIDENT_RESPONSE.md | ||
| LICENSE.md | ||
| main.go | ||
| main_test.go | ||
| README.md | ||
| SECURITY.md | ||
| Taskfile.yml | ||
| THREAT_MODEL.md | ||
| USERS.md | ||
GoReleaser
Release engineering, simplified.
We handle the complexities of releasing so you can focus in building what really matters: your software.
Get GoReleaser
Documentation
Documentation is hosted live at https://goreleaser.com
Community
You have questions, need support and or just want to talk about GoReleaser?
Here are ways to get in touch with the GoReleaser community:
You can find the links above and all others here.
Code of Conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. We appreciate your contribution. Please refer to our contributing guidelines for further information.
Badges
Contributing
This project exists thanks to all the people who contribute. Contribution guide.
Sponsoring
Does you or your company use GoReleaser?
You can help keep the project bug-free and feature rich by sponsoring the project and its maintainers.
You can sponsor GoReleaser via:
A big thank you to all current, past, and future sponsors!
