T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:46
- Finding
- Unpinned Remote Skill Installation Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md:46-73` **Vulnerability Type**: Unpinned third-party CLI and mutable remote Skill sources **Risk Level**: Medium The installation instructions execute an unversioned npm CLI through `npx` and install Skill content from mutable GitHub repository paths: ```bash npx skills add https://github.com/kcns008/cluster-agent-swarm-skills # Orchestrator - Task routing and coordination npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/orchestrator # Cluster Ops - Atlas (cluster operations) npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/cluster-ops # GitOps - Flow (ArgoCD, Helm, Kustomize) npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/gitops # Security - Shield (RBAC, policies, CVEs) npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/security # Observability - Pulse (metrics, alerts, incidents) npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/observability # Artifacts - Cache (registries, SBOM, promotions) npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/artifacts # Developer Experience - Desk (namespaces, onboarding) npx skills add https://github.com/kcns008/cluster-agent-swarm-skills/skills/developer-experience ``` ### Technical Analysis The command does not pin the `skills` npm package to a reviewed version. It also references GitHub content without an immutable commit hash, verified release artifact, checksum, or cryptographic signature. Consequently, the effective installation behavior and installed Skill instructions may change after this artifact has been audited. The project artifact contains only `SKILL.md`, although its documentation advertises additional agent definitions, scripts, and references. Those remote components were therefore unavailable for review. This does not establish that the u ...[truncated 1897 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the npm CLI to a specifically reviewed version, for example by using an exact package version rather than allowing `npx` to resolve the latest release. 2. Reference the remote repository by an immutable full commit SHA instead of a mutable default branch or directory URL. 3. Vendor the required Skill files, scripts, and references into the audited project so their complete behavior can be reviewed before installation. 4. Publish signed release artifacts and verify their cryptographic signatures or SHA-256 checksums before installation. 5. Use a lockfile and an approved internal package registry or mirror for installation tooling where practical. 6. Run installation in a sandboxed, least-privileged environment without production cluster, cloud, registry, or Git credentials. 7. Add automated dependency and repository integrity monitoring, including alerts for unexpected changes to pinned artifacts. 8. Require security review and provenance verification before updating either the pinned CLI version or repository commit.