Skip to content

Resolve the three dependency alerts with no upstream fix #198

Open

Description

@fefi95

Priority: P2

Context

No version bump fixes these three alerts, so they stay open in GitHub and Vanta until someone acts:

Do

For each package:

  • Run yarn why <pkg> to find the parent.
  • If a newer version of the parent drops it, bump or replace the parent.
  • If not, write in the PR which dev-only tool pulls it in and why it's unreachable at runtime.

Done when

Each of the three is either gone from yarn.lock or has a written justification in the PR. Someone with Vanta access then uses that justification to dismiss the alert.

Source: code audit of stackbuilders/assertive-ts at e81a614 (2026-10-13) plus open Vanta/Dependabot findings.

Activity

  1. self-assigned this
    on Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

dependenciesPull requests that update a dependency file

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions