Reliability Evidence Pack

Provides tools to record, validate, and report agent operational reliability artifacts using standardized schemas for consistent monitoring and compliance.

This package appears to do what it says: local collection, schema validation, and bundle generation for reliability artifacts. Before installing or running it: 1) Inspect the large scripts (scripts/rep.mjs, scripts/rep-validate.mjs, scripts/rep-heartbeat-cron.mjs, and github-action/entrypoint.sh) for any network calls or unexpected execs. 2) Configure REP_ARTIFACTS_PATH to an isolated, access-controlled directory and add it to .gitignore. 3) Never place private signing keys in the artifacts directory — use an external KMS/vault. 4) Prefer running the cron/heartbeat scripts in a container or unprivileged account first, and review the GitHub Action entrypoint before adding to CI. 5) If you do not want autonomous agent invocation, disable model invocation for this skill in your agent settings. If you want, I can scan the full contents of rep.mjs and rep-validate.mjs for network/system calls and highlight any lines of concern.

Package: (xpi) Version: Description: REP v1.0 demonstration bundle with mixed artifact types showcasing chain integrity, content hashing, and reliability evidence collection. The package implements a 'Reliability Evidence Pack (REP)' system designed for structured logging, validation, and auditing of agent operational data. The core logic, primarily in Node.js scripts, focuses on generating, storing, and verifying artifacts related to agent decisions, performance, health, and incidents. Key functionalities include local file system operations (reading/writing JSONL files to configurable paths), cryptographic hashing (SHA256) for artifact integrity and chain-of-custody, and comprehensive validation of artifact schemas and inter-artifact references. System information (e.g., CPU, memory, uptime, hostname, PID) is collected by specific scripts (e.g., `rep-heartbeat-cron.mjs`, `rep-performance-baseline.mjs`) but is logged locally as part of the reliability monitoring, not exfiltrated. The `rep.mjs serve` command initiates a local HTTP server to expose bundle statistics and artifacts, which includes `Access-Control-Allow-Origin: '*'`. While this could pose an information disclosure risk if exposed publicly without authentication, the project's documentation explicitly addresses this, warning about sensitive data in artifacts and recommending access control, indicating an intended use for local or controlled internal environments. No outbound network connections for data exfiltration or command-and-control are observed. External command execution is limited to controlled invocations of local scripts or package managers within a GitHub Action context. The project includes extensive documentation that clearly outlines its purpose, usage, and security considerations, reinforcing its legitimate intent. There is no evidence of obfuscation, arbitrary code execution, or other malicious behaviors. The non-functional nature of `cli/bin/cli.js` is a functional discrepancy, not a security vulnerability.