Source Availability and Licenses#
The Seesaw monorepo contains the Solana program source, clients, services, and documentation. Source being present in a checkout does not establish public repository access, an open-source license, or a published package release.
Repository access#
The repository used for this documentation is
ChrisTorresLugo/seesaw. It currently
requires authorized GitHub access. If a source link is unavailable, obtain an
authorized release checkout; do not assume a similarly named repository is the
same release.
Some package manifests still name palominito/seesaw. That older metadata does
not establish that a public repository or published package is available there.
See Installation for the checkout-based workflow and
release state. Its machine-readable inventory is docs/sdk/package-registry-status.json.
Component licenses#
| Component | License in this checkout | Source of truth |
|---|---|---|
| On-chain program | Business Source License 1.1 (BUSL-1.1) | Root LICENSE, program/Cargo.toml, and source headers |
| TypeScript core, CLI, Rust SDK, Python SDK | MIT | Each package's manifest and license file |
The program's source is included under program/src/; it is not a closed-source
binary-only component. Its Business Source License explicitly says it is not an
Open Source license. The license names Apache License 2.0 as the Change License
and specifies the change-date terms. Read the license for the permissions that
apply to the version you intend to use. MIT client licensing does not replace the
program's license, and repository access does not change either license.
Developer interface artifacts#
An authorized checkout includes the interface material needed to build and review an integration:
- Package manifests, README files, changelogs, licenses, and security policy.
- Generated client types, instruction/account builders, IDL, and source ABI.
- Program identifiers, mint and feed configuration, and PDA derivations.
- Test vectors for account derivation, instruction encoding, fees, and settlement.
- Example env files with placeholders only.
- Keeper/relay build instructions and their operator-provided dependencies.
These artifacts can be validated locally. Their presence is not evidence that a package has been published, a service is hosted, or a production release is approved.
Documentation publication boundary#
The public docs renderer deliberately excludes maintainer runbooks, incident procedures, internal audit evidence, and release signoff records. Public integration guides describe supported interfaces and operational dependencies; they do not publish credentials or internal response procedures. Publishing a docs route and making the GitHub repository public are separate decisions.