pi-mcp-extension

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.Every release is tagged in git as vX.Y.Z (https://github.com/irahardianto/pi-mcp-extension/tags) by .github/workflows/publish.yml prior to npm publication, and release tags are protected from deletion or mutation via .github/rulesets/release-tags.json.

All development occurs in the public GitHub repository (https://github.com/irahardianto/pi-mcp-extension) via feature branches, pull requests, and individual commits on main between releases.

Repository on GitHub, which uses git. git is distributed.

The project follows Semantic Versioning 2.0.0 (MAJOR.MINOR.PATCH), computed automatically from Conventional Commits by scripts/release.ts and documented in https://github.com/irahardianto/pi-mcp-extension/blob/main/CHANGELOG.md.

Every release has a unique Semantic Versioning identifier recorded in package.json, CHANGELOG.md, git tags (vX.Y.Z), and the npm registry (https://www.npmjs.com/package/pi-mcp-extension).

Non-trivial release notes file in repository: https://github.com/irahardianto/pi-mcp-extension/blob/main/CHANGELOG.md.

Release notes in https://github.com/irahardianto/pi-mcp-extension/blob/main/CHANGELOG.md
explicitly identify all security fixes and advisories under ### Security sections (for example, GHSA-6qxp-vccf-f47h in 1.9.8).

Non-trivial SECURITY[.md] file found file in repository: https://github.com/irahardianto/pi-mcp-extension/blob/main/SECURITY.md. [osps_do_02_01]

The project tracks bug reports and enhancement requests using GitHub Issues at https://github.com/irahardianto/pi-mcp-extension/issues

Bug reports submitted to https://github.com/irahardianto/pi-mcp-extension/issues
are promptly acknowledged, triaged, and resolved.

Enhancement requests in https://github.com/irahardianto/pi-mcp-extension/issues
are actively reviewed, responded to, and implemented.

All issue reports, enhancement requests, and responses are publicly archived and searchable at https://github.com/irahardianto/pi-mcp-extension/issues.

Private vulnerability reports are accepted via GitHub Private Vulnerability Reporting at https://github.com/irahardianto/pi-mcp-extension/security/advisories/new
as documented in https://github.com/irahardianto/pi-mcp-extension/blob/main/SECURITY.md.

https://github.com/irahardianto/pi-mcp-extension/blob/main/SECURITY.md establishes a response SLA of 7 business days for acknowledgment, and all security issues in the past 6 months have been responded to and patched within days.

Not applicable: the Pi coding agent executes src/index.ts directly as TypeScript at runtime, and the npm package ships src/ directly without a compilation or build step required after modifying source code.

Not applicable: no build step is required to run the software from source (packaging for npm distribution uses standard npm pack).

Not applicable: no build step is required to run the software from source (all development, typechecking, and packaging tools—Node.js, npm, TypeScript, tsx—are FLOSS).

The repository includes a FLOSS (MIT-licensed) automated test suite in tests/*.test.ts using Node's built-in node:test runner, tsx, and fast-check. Instructions to run it are documented in https://github.com/irahardianto/pi-mcp-extension/blob/main/README.md

The test suite is invoked via the standard Node.js command npm test (and npm run test:coverage).

npm run test:coverage enforces a hard coverage floor across src/** in CI (.github/workflows/ci.yml): at least 95% line coverage, 85% branch coverage, and 83% function coverage, supplemented by property-based fuzz tests in tests/fuzz.test.ts.

GitHub Actions CI (.github/workflows/ci.yml) runs the full test suite on every pull request and push to main across Node 22 and 24 on Linux, macOS, and Windows, and is enforced as a required status check in .github/rulesets/default-branch.json.

AGENTS.md and CONTRIBUTING.md require tests for all new features and bug fixes, and CI blocks merges unless npm test and the npm run test:coverage floor (95% lines / 85% branches / 83% functions) pass.

Recent features and security changes in git history include corresponding automated tests (e.g., tests/debug-log.test.ts for the opt-in debug log in v1.10.0, tests/release.test.ts for release orchestration, tests/oauth-fixes.test.ts for OAuth issuer/origin binding, and tests/fuzz.test.ts).

The requirement to add tests and pass npm test / npm run test:coverage is documented in https://github.com/irahardianto/pi-mcp-extension/blob/main/CONTRIBUTING.md
and https://github.com/irahardianto/pi-mcp-extension/blob/main/AGENTS.md.

The project uses ECMAScript modules ("type": "module", strict mode by default), TypeScript static type checking (npm run typecheck via tsc --noEmit), and type-aware ESLint (npm run lint via eslint.config.mjs).

npm run lint and npm run typecheck are required CI checks in .github/workflows/ci.yml and fail on any error or warning.

tsconfig.json enables strict: true, noUncheckedIndexedAccess: true, exactOptionalPropertyTypes: true, noUnusedLocals: true, noUnusedParameters: true, noImplicitReturns: true, noImplicitOverride: true, and noFallthroughCasesInSwitch: true. eslint.config.mjs enforces strict type-aware rules including no-floating-promises, no-misused-promises, switch-exhaustiveness-check, no-explicit-any, and no-empty.

The maintainer applies Saltzer and Schroeder's secure design principles throughout the architecture (documented in SECURITY.md, OAUTH.md, docs/ARCHITECTURE.md, and AGENTS.md): fail-safe defaults (.pi/mcp.json ignored unless ctx.isProjectTrusted() is true; debug log disabled by default), least privilege (0o600 credential/log files inside 0o700 directories; minimal GitHub Actions permissions), complete mediation and origin/issuer binding (stored OAuth state verified against canonical serverUrl and authorization server issuer), economy of mechanism (only two runtime dependencies: @modelcontextprotocol/sdk and zod), and strict allowlist validation (Zod schemas on all external inputs, URL scheme allowlists, and SAFE_FIELD_NAMES allowlist in src/debug-log.ts).

Common vulnerability classes are documented in SECURITY.md and actively mitigated with unit tests and custom Semgrep rules (.semgrep/rules/): command/shell injection (no shell interpolation; URL scheme validation before browser open), terminal escape injection (sanitizeTerminalText strips ANSI/OSC/DCS/C0/C1 sequences from server stderr and notifications), OAuth CSRF and open redirect attacks (256-bit CSPRNG state verified on both success and error callbacks, PKCE S256, loopback-only redirect URLs with explicit port), cross-origin/cross-issuer token reuse, and secret leakage (redacting logger + Gitleaks CI scan).

The software uses only standard, expert-reviewed protocols and algorithms: OAuth 2.1 with RFC 7636 PKCE (S256 / SHA-256), HTTPS/TLS via Node.js built-in fetch/OpenSSL, SHA-256 (createHash("sha256") from node:crypto), and CSPRNG random values (crypto.getRandomValues and crypto.randomUUID).

All cryptographic functions delegate to Node.js built-in node:crypto / Web Crypto APIs (backed by OpenSSL) and @modelcontextprotocol/sdk; no custom cryptographic algorithms are implemented.

All cryptographic functionality relies exclusively on FLOSS implementations: Node.js (node:crypto / OpenSSL) and the MIT-licensed @modelcontextprotocol/sdk.

All cryptographic operations meet or exceed NIST 2030 minimums (256-bit SHA-256 hashes via createHash("sha256"), 256-bit OAuth CSRF state via crypto.getRandomValues(new Uint8Array(32)), 122-bit CSPRNG UUIDv4 nonces, and Node.js 22+ default TLS 1.2/1.3 key lengths).

The software does not use or support any broken cryptographic algorithms (such as MD4, MD5, DES, RC4, or Dual_EC_DRBG) or insecure cipher modes; only SHA-256 and Node.js 22+ default TLS are used.

The software does not depend on SHA-1, CBC mode, or any weak algorithms; all hashing and PKCE challenges use SHA-256 (S256).

Outbound HTTPS connections use Node.js 22+ default TLS (TLS 1.3 and TLS 1.2 with ECDHE cipher suites), which enforces Perfect Forward Secrecy by default.

Not applicable: pi-mcp-extension is a client extension and does not authenticate inbound external users or store user passwords.

All security-sensitive random values (OAuth state parameters, PKCE verifiers, lock nonces, and temporary file suffixes) are generated using Node.js CSPRNG APIs (crypto.getRandomValues(new Uint8Array(32)) in src/authorize-flow.ts and randomUUID() from node:crypto in src/auth-lock.ts and src/oauth-state-store.ts). Math.random() is never used.

The package and source code are delivered exclusively over HTTPS via npm (https://www.npmjs.com/package/pi-mcp-extension) and GitHub (https://github.com/irahardianto/pi-mcp-extension).

No hashes or artifacts are retrieved over plain HTTP. Releases are published to npm over HTTPS with OIDC Trusted Publishing provenance attestations, and CI verifies registry signatures with npm audit signatures.

There are zero unpatched known vulnerabilities in the project or its runtime dependencies. Disclosed advisories (such as GHSA-6qxp-vccf-f47h, fixed in v1.9.8) were patched immediately, and CI runs npm audit --omit=dev --audit-level=high and dependency-review on every change.

All security vulnerabilities are patched and released immediately via automated patch releases (see CHANGELOG.md and SECURITY.md).

No valid private credentials exist in the repository or git history, continuously verified by Gitleaks in .github/workflows/secret-scan.yml (.gitleaks.toml).

Multiple FLOSS static analysis tools run in CI on every PR, push to main, and release branch before release: Semgrep (.github/workflows/semgrep.yml), zizmor and actionlint (.github/workflows/workflow-lint.yml), and type-aware typescript-eslint.

Semgrep runs the p/typescript, p/javascript, and p/github-actions security rulesets along with custom rules in .semgrep/rules/ enforcing project security invariants (banning stdout/stderr leaks, unsafe 401 substring matching, secret logging, and unsafe dependencies), while zizmor scans GitHub Actions workflows for injection, pinning, and permission vulnerabilities.

Semgrep (--error) and zizmor are required blocking status checks in CI; any finding fails the build and must be fixed before code can be merged or released.

Static analysis (semgrep.yml, workflow-lint.yml, ci.yml) runs automatically on every pull request and every push to main.

The project meets both criteria defined by Best Practices: it runs property-based fuzz testing using fast-check (tests/fuzz.test.ts) to vary inputs across parsers, schemas, URLs, and sanitizers, and runs an automated test suite with >85% branch coverage (--test-coverage-branches=85 enforced in .github/workflows/ci.yml and .github/workflows/publish.yml) before every release.

Not applicable: the project is written entirely in TypeScript/JavaScript running on Node.js (a memory-safe environment) and contains no C/C++ or other memory-unsafe code.

All dynamic test suites and fast-check property-based fuzz tests (tests/*.test.ts) execute with strict runtime assertions (node:assert/strict) and Zod runtime schema validations enabled.

All defects and edge cases discovered through automated testing and fast-check fuzzing are fixed immediately prior to release, with zero open medium or higher severity vulnerabilities.