Dear Open Source Developers: It's OK not to embargo
Web page · https://opensourcesecurity.io/2026/10-embargo
First seen by Oriel on .
AI summary
The author endorses Curl’s policy of publicly tracking low- and medium-severity vulnerabilities, arguing that fewer embargoes could reduce unsustainable workloads and burnout among open source maintainers.
- Private embargoes prevent normal workflows such as public repositories, CI testing, community review, and broad testing, while requiring complex secrecy management.
- Vulnerability discovery has become cheap and high-volume, but fixing remains expensive, leaving volunteer maintainers overwhelmed by reports.
- The author acknowledges public reports may expose unresolved bugs but argues abandoned, burned-out projects pose a greater security risk.
- Projects should adapt Curl’s policy to their needs, potentially limiting embargoes to critical vulnerabilities or eliminating them entirely.
- Open source software is provided “AS IS,” so maintainers may reject urgent demands unless users contribute funding, employment, or other support.
#open source security #vulnerability disclosure #security embargoes #maintainer burnout
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 33, latest observation ; +32 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 4, latest observation ; +4 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | lhovnm | https://opensourcesecurity.io/2026/10-embargo/ Read discussion |