Skip to content

Security: rhyanvargas/agentic-development-starter-kit

Security

Report a vulnerability

SECURITY.md

Security Policy

Supported versions

Security fixes are applied to the latest release on main and the most recent semver tag when practical.

Reporting a vulnerability

Please do not open a public GitHub issue for security-sensitive reports.

Prefer one of:

  1. GitHub Private vulnerability reporting on this repository (Security tab), if enabled.
  2. Email the maintainers listed in the GitHub repo profile / recent release notes.

Include:

  • Description of the issue and impact
  • Steps to reproduce (or proof-of-concept)
  • Affected paths (skills, scripts, install docs)
  • Whether the issue involves recommended upstream skills (if so, name the source)

Dependency security

This repository uses free GitHub Dependabot, npm audit CI, and Socket:

  • Dependabot version updates: .github/dependabot.yml — weekly npm (root workspace / create-adsk) and GitHub Actions updates
  • Dependabot alerts + security updates: enable once in the GitHub Security tab (not fully encoded in YAML)
  • CI audit gate: .github/workflows/skills-ci.yml runs npm ci then npm audit --audit-level=high on every PR and push to main
  • Socket for GitHub: org/repo app for PR dependency comments
  • Socket CI: .github/workflows/socket.yml runs socketcli when SOCKET_SECURITY_API_KEY is set (repo or org secret)

Local check:

npm ci && npm audit --audit-level=high

Socket policy (this repo)

Success criterion is policy-clean PR gates, not a perfect 100 on every Socket package-health gauge for create-adsk (a CLI that writes files and spawns npx skills will keep filesystem/shell capability signals).

Alert class Default stance Notes
Known malware / AI malware / typosquat / obfuscated code Block Never merge
Install scripts (postinstall / preinstall on published deps) Block create-adsk must not ship consumer install scripts
Git / HTTP / GitHub URL dependencies Block Prefer registry + lockfile
Telemetry / protestware Block
New High capability creep (network, eval, env harvest) without justification Block Document exception in PR if truly required
Filesystem access / shell access in create-adsk Monitor / warn Expected for adopter CLI; do not “fix” by removing product behavior
Recently published / new author / low downloads on brand-new packages Monitor Cool-down + reputation; not a merge blocker by itself
Wildcard (^/~) ranges on published create-adsk production deps Warn → fix Prefer exact pins in packages/create-adsk/package.json

Maintainer bootstrap (once):

  1. Install Socket for GitHub on this repo (done if you already see Socket PR comments).
  2. Create a Socket API token and add GitHub Actions secret SOCKET_SECURITY_API_KEY (repo or org).
  3. In the Socket dashboard, align org/repo policy with the table above (block vs warn).
  4. Optional: require the socket-security check in branch protection after the secret is live.

Agent playbook: first-party skill supply-chain-gate (/setup-socket).

npm Trusted Publishing (create-adsk)

The create-adsk package publishes from GitHub Actions with npm Trusted Publishing (OIDC) — no long-lived NPM_TOKEN in repo secrets. Provenance attestations are enabled via publishConfig.provenance.

Artifact Role
.github/workflows/publish-create-adsk.yml OIDC publish on create-adsk-v* tags (or manual workflow_dispatch)
packages/create-adsk/package.json publishConfig.access + provenance

Maintainer bootstrap (once): npm requires the package name to exist before Trusted Publisher can be configured. Publish a one-time placeholder (e.g. 0.0.0) or the first real version with an interactive npm login / short-lived token, then on npmjs.com → package Settings → Trusted Publisher:

  • Organization or user: rhyanvargas
  • Repository: agentic-development-starter-kit
  • Workflow filename: publish-create-adsk.yml (filename only)
  • Allowed actions: npm publish

After Trusted Publisher works, prefer restricting token publish access on the package (npm “disallow tokens” / 2FA settings). Day-to-day release steps: docs/RELEASE.md.

Child process (create-adsk)

create-adsk must not call spawn/execFile with both an args array and shell: true (Node DEP0190). On Windows, npx/npm run via cmd.exe /d /s /c with shell: false and escaped arguments (see packages/create-adsk/src/skills.ts).

Skill supply-chain guidance

ADSK recommends (but does not vendor) third-party skills. Treat unpinned installs from public skill registries as untrusted until reviewed:

  • Prefer official orgs and pinned versions in recommended-skills.json
  • Review SKILL.md and any scripts/ before enabling in production environments
  • Do not install skills that request credentials, broad network exfiltration, or opaque binaries without review

See docs/lifecycle-coverage.md for trust criteria.

There aren't any published security advisories