Next liveBuild Your Chief of Staff · OnlineSave your seat →
Factory Platform

Software Factory Dependency Security

How the software factory keeps a project's Deno, Svelte, SvelteKit, Vite and npm dependencies patched: the baseline files, the tickets it opens, and what never merges on its own.

|View as Markdown
Hunter Hodnett
Co-founder and co-CEO
||1 min read
#alchemist#security#dependencies#tickets#platform

Every software factory project that uses Deno, Svelte, SvelteKit, Vite, npm or JSR gets the same dependency security rules. Chipp checks your project’s dependencies on a schedule and opens tickets in your project when something needs attention. It never pushes to your default branch and never merges a major update on its own.

What a new project gets

A new project starts with four files, built from the manifests it has:

  • .github/dependabot.yml asks Dependabot for weekly update pull requests. Patch and minor updates are grouped. Major updates are held back.
  • .github/workflows/dependency-audit.yml runs deno audit and npm audit every week and whenever a manifest changes. It fails the run when a dependency has a known advisory.
  • .github/workflows/dependabot-auto-merge.yml can merge Dependabot patch and minor updates. It does nothing until you set the repository variable DEPENDENCY_AUTO_MERGE to true. Even then it merges only when the update changes manifests and lockfiles alone, and only when your default branch has required status checks.
  • docs/dependency-security.md explains these rules to your project’s agents.

A project created from a template that holds no supported manifest gets none of these. A project on Chipp-hosted git does not run GitHub Actions, so it gets none either.

Tickets Chipp opens

Chipp reads your repository with a read-only, repository-scoped token. It sends only package names and versions to the public advisory database. For each problem it opens one ticket in your project, in the Security category:

  • Security fix. One ticket per package and target version, listing the advisories, the installed and fixed versions, and the steps. Critical and high advisories, and advisories with no severity, are marked high priority in the title and body.
  • Major migration. One ticket when a Deno, Svelte, SvelteKit or Vite major update is needed, either because an advisory has no fix in your current major or because your major is no longer supported. See the next section.
  • Baseline. One ticket when your project is missing the files above. It carries the files. A file you already have is never overwritten: merge the missing parts into it.

Each finding is ticketed once. A later scan does not open it again. If an advisory stops applying, Chipp marks it resolved.

Tickets use your project’s credit like any other ticket. If your organization has no credit, Chipp waits and opens the ticket on a later scan.

The major migration ticket

Every major migration ticket has the same eight sections, so you can review it quickly and an agent can run it without asking you anything:

  1. Summary. Your project and repository, the framework, the exact current and target versions, why the move is needed (a security advisory, the end of support, or both), and its priority.
  2. Authoritative sources. The official migration guide, the release notes for every major in between, the advisory or support policy, and the plugin and adapter guides. Each link shows the date Chipp checked it. Chipp cites only links that answered.
  3. Scope and likely affected files. The real files in your repository: runtime pins, manifests and lockfiles, Svelte and Vite configuration, hooks, routes, plugins, deployment files, tests and docs.
  4. Step-by-step migration checklist. From a clean branch and a recorded baseline to updated docs.
  5. Test and verification plan. Checks, build, smoke tests and post-deploy monitoring.
  6. Rollout plan. Chipp first, then one canary project, then the rest. Each project has its own ticket.
  7. Rollback plan. The last known good commit and one combined revert.
  8. Acceptance criteria. The new version is pinned, the old one is gone, and the checks pass.

Chipp does not guess. If a version, the reason or an official source is missing, it does not create the ticket for that framework. The scan reports the project and what is missing.

Migration tickets wait for you. Chipp puts each one in your project’s approval queue. Edit any line you like, then approve it to start the work, or reject it. A rejected migration is not proposed again. A new major version, or a different current major, is a new migration.

What never happens automatically

  • A major update is never merged without a person reviewing it. Chipp checks the versions as well as the update label, so a mislabeled major is still held.
  • A major migration never starts until you approve it.
  • Chipp never pushes to your default branch.
  • Chipp never reads one project’s repository, dependencies or tickets while handling another project.

What is not checked

  • JSR packages have no public advisory feed, so JSR imports are not checked for advisories.
  • The Deno runtime is checked against the support policy only.
  • An npm manifest with no lockfile cannot be checked. The scan names it so you can add a lockfile.

For how tickets run, see Software Factory Tickets.