← Home

@verdaccio/hooks

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

sergiohgzverdaccio.npmjotadeveloperverdacciopack

Keywords

privatepackagerepositoryregistryenterprisemodulesproxyserververdaccio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Verdaccio migrated to GitHub Actions CI publishing with SLSA attestation; this is a legitimate infra change for the monorepo. ai
maintainer-change maintainer-added AI (maintainer-change): verdacciopack addition aligns with the org's CI/CD publishing transition; no malicious indicators present. ai
dependencies unvetted-dep:handlebars AI (dependencies): handlebars is a well-known, widely-used templating library; its use here is expected for notification templating in Verdaccio hooks. ai
provenance no-provenance AI (provenance): Established Verdaccio monorepo package; provenance absence is consistent across all versions and not a risk indicator here. ai

Versions (showing 3 of 3)

Version Deps Published
8.0.2 5 / 5
8.0.1 5 / 5
8.0.0 5 / 5

v8.0.2

2 findings
HIGH Publisher changed: verdaccio.npm → GitHub Actions (on 2026-05-25) provenance

This version was published by a different npm account than previous versions on 2026-05-25. 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.

v8.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.0

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.