Open source and community
SCPN Studio is built in the open. The Hub core, platform SDK, and independent verifier are available under a dual AGPL-3.0 / commercial licence.
Repositories
The open layers of the SCPN Studio federation.
SCPN Studio
The federating Hub, portal, and web shell that catalogue studios and verify seals in the browser.
AGPL-3.0-or-later / commercial
SCPN Studio Platform
The domain-neutral Python SDK: evidence bundles, manifests, verbs, identity, jobs, and seal ceremonies.
AGPL-3.0-or-later / commercial
@anulum/verify
The standalone TypeScript seal verifier used by the Hub and available from the command line.
AGPL-3.0-or-later / commercial
SC-NeuroCore
Reference neuromorphic studio and the first live federation remote.
AGPL-3.0-or-later / commercial
SCPN-Control
Control-theory studio with formally bounded claim boundaries.
AGPL-3.0-or-later / commercial
Governance
How we work, report problems, and licence the code.
Contributing
How to report issues, propose changes, run the gates, and submit pull requests.
Code of Conduct
Expected behaviour and the process for reporting unacceptable conduct.
Security policy
How to report vulnerabilities privately and our disclosure timeline.
Licence
Dual-licensed under AGPL-3.0-or-later with a commercial option.
Community channels
Where to ask questions and report issues.
GitHub issues
Bug reports, feature requests, and design discussion.
Direct questions and coordination with the maintainers.
Repository health
- Licence AGPL-3.0-or-later with commercial option
- Open governance Contributions, code of conduct, and security policy are published.
- Independent verification Seals and keyrings can be verified with the open @anulum/verify CLI.
- Reproducible builds Manifests and evidence bundles are content-addressed and reproducible.
Get involved
Start with the SDK documentation, read the trust model, then open an issue or pull request on GitHub . We review contributions against the same evidence-honesty and coverage standards we apply to the studios themselves.