triss-coworker

Pre-1.0 project distributed via npm with a single supported line; users upgrade with npm using CHANGELOG.md and semver guidance. No widely-used older versions currently require separate maintenance.

The project uses GitHub Issues as its issue tracker for bugs, enhancements, and planning: https://github.com/ayleen/triss-coworker/issues. Contributor and support docs (CONTRIBUTING.md, SUPPORT.md) direct users to the tracker, and every merged change is traceable to an issue or pull request against the same tracker. Dependabot and CI also report their results through pull requests on the same GitHub tracker.

No externally reported vulnerabilities have been resolved in the last 12 months; reporters will be credited in release notes when reports occur.

SECURITY.md documents the vulnerability response process: private reporting via GitHub Security Advisories, a fallback contact path, and what not to include in public issues: https://github.com/ayleen/triss-coworker/blob/main/SECURITY.md#reporting-vulnerabilities

eslint.config.js (ESLint flat config) defines the JavaScript style and quality rules; CONTRIBUTING.md requires npm run lint and npm run check before submission: https://github.com/ayleen/triss-coworker/blob/main/eslint.config.js

CI enforces the ESLint configuration with a zero-warning threshold on every pull request and push: https://github.com/ayleen/triss-coworker/blob/main/.github/workflows/test.yml

Pure JavaScript npm package; no native compilation or compiler/linker flags are involved.

Interpreted JavaScript distributed as source; there is no compiled debug information to preserve.

All build steps are npm scripts driven from the repository root; there is no recursive make-style build system.

npm ci against the committed package-lock.json produces a deterministic dependency tree with no native compilation: https://github.com/ayleen/triss-coworker/blob/main/package-lock.json

Standard npm distribution: npm install -g triss-coworker (or npx triss-coworker without installing); uninstall with npm uninstall -g triss-coworker. Documented in the README installation section: https://github.com/ayleen/triss-coworker#installation

Installation is a standard npm package install; filesystem staging variables such as DESTDIR do not apply.

CONTRIBUTING.md documents the developer quick start: git clone, npm install, npm test, npm run check, with lint and test guidance: https://github.com/ayleen/triss-coworker/blob/main/CONTRIBUTING.md#test-and-lint

package-lock.json is the computer-processable list of direct and transitive dependencies, and THIRD_PARTY_NOTICES documents bundled third-party components: https://github.com/ayleen/triss-coworker/blob/main/package-lock.json

Dependabot monitors npm and GitHub Actions dependencies weekly and opens update pull requests; CodeQL and gitleaks also run in CI: https://github.com/ayleen/triss-coworker/blob/main/.github/dependabot.yml

All reused components are standard npm dependencies managed with semver ranges and updated through Dependabot pull requests (recent dependabot update commits are in the repository history).

The code targets current Node.js LTS built-in APIs; ESLint flags deprecated APIs during lint, and deprecated project interfaces are tracked explicitly: https://github.com/ayleen/triss-coworker/blob/main/docs/deprecations.md

GitHub Actions runs the full automated test suite (unit, integration, and property-based fuzz tests) on every push and pull request to main, with public results: https://github.com/ayleen/triss-coworker/actions/workflows/test.yml

The project follows docs-first TDD: fixes land together with focused regression tests (for example, the OpenCode2 session lifecycle fix in PR #85 and the fast-check fuzz suite in PR #97). Substantially all bugs fixed in the last six months received regression tests.

c8 coverage over src/** is measured and enforced in CI on every PR and push (statements/lines/functions >= 80%, branches >= 75%; currently 88.2% statements, 81.1% branches, 88.86% functions): https://github.com/ayleen/triss-coworker/blob/main/.github/workflows/test.yml

CONTRIBUTING.md states the test policy for changes: run npm test and npm run check, tests must not call live external services, and tests must not be weakened to preserve undocumented behavior: https://github.com/ayleen/triss-coworker/blob/main/CONTRIBUTING.md#test-and-lint

CONTRIBUTING.md states the policy for behavior changes: document the public contract first, add focused failing coverage, implement the smallest passing change, and only then run the full suite; tests must not be weakened to preserve undocumented behavior (https://github.com/ayleen/triss-coworker/blob/main/CONTRIBUTING.md). npm run check runs lint, syntax checks, the full test suite, and docs/package gates before every PR, and CI enforces the same on Node 22 and 24 (https://github.com/ayleen/triss-coworker/blob/main/.github/workflows/test.yml).

Linter output is treated as errors: ESLint runs with --max-warnings=0 in npm run lint, so any warning fails the build both locally and in CI on every pull request and push (Node 22 and 24 matrix). Node syntax checking (npm run typecheck) plus docs and package consistency gates run alongside. The strict configuration lives at https://github.com/ayleen/triss-coworker/blob/main/eslint.config.js

THREAT_MODEL.md documents secure design principles applied in the codebase: fail-closed enforcement when required checks cannot be established, deny-first allowlists for coder engine commands, least-privilege release jobs with OIDC, and path-safety sandboxing in MCP mode: https://github.com/ayleen/triss-coworker/blob/main/THREAT_MODEL.md

The software implements no cryptographic primitives of its own. All transport security is TLS from Node.js/undici with default certificate verification — the codebase contains no strictSSL, rejectsUnauthorized, or NODE_TLS_REJECT_UNAUTHORIZED overrides. Release integrity uses npm provenance attestations plus GPG-signed release tags verified fail-closed against a committed public key. Credentials live in mode-0600 files or environment variables, are never logged, and gitleaks scans CI. No known-weak algorithms (MD5/SHA-1 for security purposes, DES, RC4, SSL, TLS < 1.2) are used anywhere: https://github.com/ayleen/triss-coworker/blob/main/SECURITY.md

The project performs no application-level cryptographic algorithm selection; transport security is delegated to Node.js, GitHub, and npm TLS defaults, so there is no algorithm inventory to rotate.

API credentials are loaded from environment variables or user configuration files written with mode 0600 (see src/coder-models.js), are never written to logs, and gitleaks scans CI for accidental exposure.

All network paths (model providers, tracker integrations, update checks) use HTTPS; the passive update check is documented and can be disabled with TRISS_UPDATE_CHECK=0: https://github.com/ayleen/triss-coworker/blob/main/SECURITY.md#standalone-update-trust-and-integrity

Network calls use Node.js fetch/undici with default TLS 1.2+ support; no protocol downgrades or minimum-version overrides are configured.

TLS certificates are verified by default on every outbound network call; the codebase contains no strictSSL, rejectsUnauthorized, or NODE_TLS_REJECT_UNAUTHORIZED overrides.

Credentials are only transmitted over certificate-verified HTTPS connections to the configured providers and registries.

npm packages are published with --provenance (Sigstore attestations), and the release workflow fails closed unless the provenance attestation is present and verified before promotion: https://github.com/ayleen/triss-coworker/blob/main/.github/workflows/publish.yml

Release version tags are annotated and GPG-signed. The publish pipeline verifies each tag's signature fail-closed against the public key committed in the repository before anything is published — the v0.41.1 release (2026-08-29) was published through this gate with a good signature from the committed key (see the release-gates job of the publish workflow). Signing setup and procedure: https://github.com/ayleen/triss-coworker/blob/main/docs/releasing.md

Untrusted inputs are validated: MCP tool inputs pass zod schemas (src/mcp/tools.js), coder engine commands pass deny-first allowlists, and URL fetching enforces an SSRF DNS guard: https://github.com/ayleen/triss-coworker/blob/main/src/mcp/tools.js

The software is a CLI and a stdio MCP server with no long-running network daemon, so there is no exposed service surface to harden beyond the existing path-safety sandbox and command allowlists.

THREAT_MODEL.md provides the assurance case: assets, trust boundaries, attacker capabilities, and countered weaknesses through documented security expectations and explicit non-guarantees: https://github.com/ayleen/triss-coworker/blob/main/THREAT_MODEL.md

CodeQL static analysis with the javascript-typescript and actions query suites runs on every pull request and push to main, targeting common vulnerability classes such as injection, path traversal, and unsafe deserialization (results at https://github.com/ayleen/triss-coworker/security/code-scanning). In addition, ESLint enforces security-relevant rules with a zero-warning threshold in CI, gitleaks scans for leaked credentials, and lockfile gates run in the test workflow: https://github.com/ayleen/triss-coworker/blob/main/.github/workflows/test.yml

Dynamic analysis runs on every push and pull request. The CI test workflow executes the full node --test suites, including the property-based fuzz suite test/fuzz.test.js (fast-check), which generates dynamic inputs for the SSRF address classifier and its literal parsers in src/net.js and checks the implementation against an independent reference oracle. Beyond unit tests, the release pipeline builds the standalone artifact twice from independent production installs and smokes it on Ubuntu and macOS (Node 22/24), and a pnpm consumer-install smoke test exercises the packed npm tarball end to end. All of these assert expected outcomes with node:assert (assertions enabled) and fail the build on any mismatch: https://github.com/ayleen/triss-coworker/blob/main/test/fuzz.test.js and https://github.com/ayleen/triss-coworker/blob/main/.github/workflows/test.yml