Open Source Software Library

A local-first editor built for you and your agents. Edit and preview Markdown, HTML, CSS, CSV, JSON, DOCX, XLSX, PDF, media, and 3D files. Work with local folders; files stay local unless you choose Cloud. Built-in Git, terminal, and agents including Codex, Claude Code, Cursor, and OpenCode. Optional Puppyone Cloud for hosting, backup, and always-on MCP or CLI access. Apache License 2.0. Install: npm install --global puppyone (macOS Desktop).

An Indy Tails Server is file server that is designed to receive, store and serve Hyperledger Indy Tails files. Indy tails files are generated by an issuer of Indy AnonCred verifiable credentials when a Revocation Registry is created and must be published to a location accessible by all holders that receive a credential referenced in that Revocation Registry. The generated file is static, it does not change, and the credential holders use the tails file to produce a zero-knowledge proof of non-revocation about their credential and include it when responding to a proof request with a proof that includes claims from a revocable credential. If you are new to Indy AnonCreds Revocation, please review this document to understand how Indy revocation works, and where tails files fit in. An Indy Tails Server is a customized file server that makes it easy for AnonCred Issuers to publish tails files and for holders to access those tails files. A tails file does not have to be published to an Indy Tails Server, they can be published anywhere as long as there exists a URL accessible to all holders to access the tails file. If holders are mobile iOS or Android apps, the URL must use SSL (e.g. must be https:) due to the restrictions in those OS's. Support for publishing tails files to an Indy Tails Server is built into Aries Cloud Agent Python.

Tools and policy checks that help Government of Canada teams evaluate IBM Cloud deployments against common cloud guardrails. It is useful for repeatable compliance reviews, documentation of security expectations, and sharing implementation patterns across departments.

Open Policy Agent guidance and configuration examples for checking Google Cloud Platform services against Government of Canada cloud guardrails. The repository documents recommended settings and gives teams a reusable starting point for compliant GCP deployments.

PowerShell-based tooling for assessing Microsoft Azure environments against Government of Canada cloud guardrail requirements. Although archived, it remains a useful reference for Azure compliance automation and policy-as-code patterns.

Terraform and infrastructure templates for accelerating Government of Canada service delivery on Google Cloud Platform. The project packages reusable baseline patterns so teams can start cloud projects with consistent security and operational defaults.