AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

open-sourcing

This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering secrets hygiene, licensing, documentation, CI, and language-specific packaging.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read trailofbits--open-sourcing at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 9

references/trailofbits.md

Trail of Bits Profile

Apply this guidance in addition to the generic workflow when scripts/detect_org.sh prints trailofbits. Everything in this file is public information; internal process details (credentials, announcement workflow, release sign-off) live in Trail of Bits' internal documentation, which the maintainer should consult directly.

License policy

  • Default to Apache 2.0 for nearly all projects.
  • Use AGPLv3 when the project would offer a significant advantage to competitors who modify it without contributing changes back.
  • Use Creative Commons for non-code work:
  • When in doubt, confirm with the project manager or an existing open-source maintainer before publishing.

Copyright line convention (current year only, no ranges):

Copyright (c) 2026 Trail of Bits <[email protected]>

For forks and adopted projects, add this line under the existing copyright rather than relicensing, unless the changes involve the company's competitive interests (see the AGPLv3 criterion above).

Repository location

Official projects live in the trailofbits GitHub organization. Related ecosystems use lifting-bits (binary lifting) and crytic (smart contract tooling). Move personal repositories into the appropriate organization before announcing them.

Package publishing

Publish under the company's shared accounts so ownership survives individual departures:

  • PyPI: add the trailofbits organization as an owner of the package.
  • RubyGems: add the trailofbits account as a gem co-owner.
  • Prefer trusted publishing (OIDC from GitHub Actions) over long-lived API tokens on every index that supports it (PyPI, RubyGems, crates.io).

Account access is handled internally; consult the internal documentation rather than creating parallel accounts.

Project scaffolding

  • Python: generate new projects with cookiecutter-python, which encodes current company practices: uv, ruff, ty, prek, pdoc, SHA-pinned CI audited by zizmor, trusted publishing with SLSA provenance, and 100% coverage and docstring-coverage gates. Generated projects also ship AGENTS.md agent instructions. The modern-python skill in this marketplace covers the same toolchain.
  • Example repositories for release automation: pe-parse (C++/CI-managed packaging) and pip-audit (Python/trusted publishing).

Before flipping the repository public

Beyond the generic checklist, Trail of Bits maintainers should:

  1. Confirm the license choice with their project manager if it deviates from Apache 2.0.
  2. Follow the internal public-release checklist and announcement process (blog post, social media) documented internally — public release is often paired with an announcement, and coordinating that before the repository goes public preserves the option.