[SECURITY][LOW] No pnpm audit step in CI — supply chain vulnerabilities not auto-detected

Open Beginner friendly
#63 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Start by inspecting the CI workflow files under .github/workflows/ in both repositories and the committed pnpm-lock.yaml files. Check how pnpm is installed and dependencies are currently checked, then add the requested audit coverage and verify the workflow runs pnpm audit with the specified severity threshold. Done means the CI pipeline performs the vulnerability audit successfully.

Written by the indexing model from the issue text.

Description

area: backend bug priority: P3 security triaged

Summary

Both repos use pnpm and have pnpm-lock.yaml committed (good). However, no CI pipeline runs pnpm audit. Without automated audit, newly disclosed CVEs in dependencies like nano (CouchDB client), ws, fastify, vite, or serve will not be detected until a manual audit is run. The pnpm-lock.yaml pins all transitive deps, but vulnerability databases update daily.

CVSS Score

3.1 (Low) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Category

OWASP A06 — Vulnerable and Outdated Components

Affected File(s)

  • .github/workflows/ (missing audit step)
  • pnpm-lock.yaml

Remediation

Add a CI step to both repos:

- name: Dependency vulnerability audit
  run: pnpm audit --audit-level=moderate

Also consider enabling Dependabot or Renovate on both GitHub repos for automated dependency update PRs.

References

Dominant language
TypeScript
Stars
23
Forks
13
Avg merge
1d 7h
Merged PRs (30d)
95

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Eyevinn/open-live

All issues in Eyevinn/open-live

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.