Maintainx Ci IntegrationSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| cursor | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: maintainx-ci-integration description: 'Integrate MaintainX API testing into CI/CD pipelines. Use when setting up automated testing, configuring CI workflows, or implementing continuous integration for MaintainX integrations. Trigger with phrases like "maintainx ci", "maintainx github actions", "maintainx pipeline", "maintainx automated testing", "maintainx ci/cd". ' allowed-tools: Read, Write, Edit, Bash(npm:*), Grep version: 1.11.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - maintainx - api - testing - ci-cd compatibility: Designed for Claude Code --- # MaintainX CI Integration ## Overview Configure CI/CD pipelines for MaintainX integrations with unit tests (mocked), integration tests (live API), and automated quality gates. ## Prerequisites - Git repository with MaintainX integration - GitHub Actions (or GitLab CI) - Test environment MaintainX API key stored as CI secret ## Instructions ### Step 1: GitHub Actions Workflow ```yaml # .github/workflows/maintainx-ci.yml name: MaintainX Integration CI on: push: branches: [main, develop] pull_request: branches: [main] env: NODE_VERSION: '20' jobs: unit-tests: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: ${{ env.NODE_VERSION }} cache: npm - run: npm ci - run: npm run test -- --coverage - uses: actions/upload-artifact@v4 with: name: coverage path: coverage/ integration-tests: runs-on: ubuntu-latest needs: unit-tests environment: staging steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: ${{ env.NODE_VERSION }} cache: npm - run: npm ci - run: npm run test:integration env: MAINTAINX_API_KEY: ${{ secrets.MAINTAINX_API_KEY_STAGING }} MAINTAINX_ENV: staging - run: npm run lint - run: npm run typecheck security-scan: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Scan for secrets run: npx gitleaks detect --source . --no-git --verbose - name: Audit dependencies run: npm audit --production --audit-level=high ``` ### Step 2: Unit Tests with Mocked API ```typescript // tests/work-orders.test.ts import { describe, it, expect, vi, beforeEach } from 'vitest'; import axios from 'axios'; vi.mock('axios'); describe('Work Order Service', () => { beforeEach(() => { process.env.MAINTAINX_API_KEY = 'test-key'; vi.resetAllMocks(); }); it('creates a work order with required fields', async () => { const mockWO = { id: 1, title: 'Test WO', status: 'OPEN', priority: 'LOW' }; vi.mocked(axios.create).mockReturnValue({ post: vi.fn().mockResolvedValue({ data: mockWO }), interceptors: { response: { use: vi.fn() } }, } as any); const { MaintainXClient } = await import('../src/client'); const client = new MaintainXClient(); const result = await client.createWorkOrder({ title: 'Test WO' }); expect(result.data.id).toBe(1); expect(result.data.status).toBe('OPEN'); }); it('handles 429 rate limit with retry', async () => { const rateLimitErr = { response: { status: 429, headers: { 'retry-after': '1' } }, isAxiosError: true, }; const successResponse = { data: { id: 2, title: 'Retried' } }; const postMock = vi.fn() .mockRejectedValueOnce(rateLimitErr) .mockResolvedValueOnce(successResponse); vi.mocked(axios.create).mockReturnValue({ post: postMock, interceptors: { response: { use: vi.fn() } }, } as any); // Test that retry logic eventually succeeds const { MaintainXClient } = await import('../src/client'); const client = new MaintainXClient(); // Wrap with retry logic from sdk-patterns const result = await withRetry(() => client.createWorkOrder({ title: 'Retried' })); expect(result.data.id).toBe(2); }); it('validates work order status transitions', () => { const validTransitions: Record<string, string[]> = { OPEN: ['IN_PROGRESS', 'CLOSED'], IN_PROGRESS: ['ON_HOLD', 'COMPLETED', 'CLOSED'], ON_HOLD: ['IN_PROGRESS', 'CLOSED'], COMPLETED: ['CLOSED'], CLOSED: [], }; expect(validTransitions['OPEN']).toContain('IN_PROGRESS'); expect(validTransitions['CLOSED']).not.toContain('OPEN'); expect(validTransitions['IN_PROGRESS']).toContain('ON_HOLD'); }); }); ``` ### Step 3: Integration Tests (Live API) ```typescript // tests/integration.test.ts import { describe, it, expect, beforeAll, afterAll } from 'vitest'; const INTEGRATION = process.env.INTEGRATION === 'true'; describe.skipIf(!INTEGRATION)('MaintainX Integration', () => { let client: any; let testWorkOrderId: number; beforeAll(async () => { const { MaintainXClient } = await import('../src/client'); client = new MaintainXClient(); }); it('authenticates successfully', async () => { const { data } = await client.getUsers({ limit: 1 }); expect(data.users).toBeDefined(); }); it('creates and retrieves a work order', async () => { const { data: created } = await client.createWorkOrder({ title: `CI Test - ${new Date().toISOString()}`, description: 'Automated CI test. Safe to delete.', priority: 'LOW', }); testWorkOrderId = created.id; expect(created.id).toBeGreaterThan(0); const { data: fetched } = await client.getWorkOrder(created.id); expect(fetched.title).toContain('CI Test'); }); afterAll(async () => { // Clean up test work order if (testWorkOrderId) { try { await client.updateWorkOrder(testWorkOrderId, { status: 'CLOSED' }); } catch { /* ignore cleanup errors */ } } }); }); ``` ### Step 4: Quality Gates ```json { "scripts": { "test": "vitest run", "test:integ
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__maintainx-ci-integration.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Maintainx Ci Integration skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Maintainx Ci Integration safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Maintainx Ci Integration access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Maintainx Ci Integration work with?
Its documentation mentions claude-code and cursor. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.