Use npm ci instead of npm install in linting workflow

[Copilot]

npm install standard in the linting workflow is non-deterministic — it can fetch updated versions and mutate package-lock.json, leading to inconsistent CI builds (CWE-829).

Changes

• .github/workflows/linting.yml: Replace npm install standard with npm ci
  • standard is already a devDependency in package.json, so npm ci installs it (and all deps) from the lockfile — no separate install step needed
  • npm ci enforces lockfile consistency and fails fast if package-lock.json is out of sync with package.json

- - run: npm install standard
+ - run: npm ci

[Copilot]

Pull request overview

Updates the linting GitHub Actions workflow to use deterministic dependency installation, reducing the risk of CI drift from fetching unintended dependency updates.

Changes:

• Replaces npm install standard with npm ci in the linting workflow.
• Relies on the existing package-lock.json and devDependencies (including standard) to ensure reproducible installs.

Show a summary per file

File	Description
.github/workflows/linting.yml	Switches lint job dependency installation to npm ci for lockfile-driven, deterministic installs.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0