Trust fosters responsibility
Trust & Safety Library - Trust & Safety Professional Association
Welcome to the Trust & Safety Library! We use this space to collect articles, blog posts, journal articles, lectures, podcasts, and websites that trust and safety professionals may find useful in developing policies, supporting moderators, building systems to detect violations, and generally deepening their practice. We welcome your submissions and feedback. This project was initially
Contributor Covenant | Contributor Covenant 3
The most widely adopted code of conduct in open source. Stewarded by the Organization for Ethical Source.
tuicr - TUI for Code Reviews
crawshaw - 2026-05-07
The industry-established code review process, review-then-commit, was a straightforward mechanism that allowed a relatively low-trust group of engineers to collaborate. It appears to have been initially developed for the Apache server OSS project in the 90s, corporatized by Google in the early 2000s, and popularized throughout the industry by several means, most notable of which was the GitHub PR.
Reflections on trusting trust
To what extent should one trust a statement that a program is free of Trojan horses? Perhaps it is more important to trust the people who wrote the software.
AI, open code and vulnerability risk in the public sector
Guidance for safely publishing source code in the open, and reducing the risk of AI-accelerated vulnerability discovery.
A method for giving credit to organizations that contribute code to Open Source
By tracking organizational contributions in Git commits, we can give organizations more tangible reasons to fund open source and help sustain it over time.
An Update on OpenPRoT
Sustainable Open Source: The Maintainers Perspective or: How I Learned to Stop Caring and Love Open Source
Better tools made Copilot code review worse. Here's how we actually improved it.
How migrating Copilot code review to shared Unix-style code exploration tools reduced review cost by reshaping agent workflows around pull request evidence.
Open Source Software and Corporate Influence — Andrew Lilley Brinker
Open source software projects are frequently enmeshed with the interests of corporations. We should update mental models of who works on open source accordingly, and build or modify power structures to be more resilient to corporate capture.
Study finds AI tools made open source software developers 19 percent slower
Coders spent more time prompting and reviewing AI generations than they saved on coding.
The Few, the Tired, the Open Source Coders
The open source movement runs on the heroic efforts of not enough people doing too much work. They need help.
