← Home

errorstacks

2
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

marvinhagemeister

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions publishing with SLSA provenance; consistent with legitimate CI/CD automation by the original author. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD-attested publish with no code changes; low-risk maintenance update pattern. ai

Versions (showing 2 of 2)

Version Deps Published
2.4.2 0 / 12
2.4.1 0 / 12

v2.4.2

2 findings
HIGH Publisher changed: marvinhagemeister → GitHub Actions (on 2026-05-17) provenance

This version was published by a different npm account than previous versions on 2026-05-17. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.