← Home

hookified

npm Repository Homepage

Event Emitting and Middleware Hooks

10
Versions
MIT
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

jaredwray

Keywords

hookseventemittereventemitter3middlewareeventshooksevent-hookshook-systemevent-drivenevent-emitterhook-handlersmiddlewareemitevent-managementbefore-after-hooksevent-listenerscustom-hookshook-utilitiestypescript-hooks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): CI/CD publish via GitHub Actions with SLSA provenance; gitHead absence is a known GHA artifact. ai
provenance publisher-changed AI (provenance): Transition from manual to GitHub Actions CI/CD publishing; SLSA attestation confirms legitimacy. ai

Versions (showing 10 of 10)

Version Deps Published
3.0.0 0 / 15
2.2.0 0 / 15
2.1.1 0 / 15
2.1.0 0 / 15
2.0.1 0 / 15
2.0.0 0 / 15
1.15.1 0 / 15
1.15.0 0 / 15
1.14.0 0 / 15
1.13.0 0 / 15

v3.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: jaredwray → GitHub Actions (on 2026-05-24) provenance

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

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.15.1

1 finding
LOW No provenance attestation provenance

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

v1.15.0

1 finding
LOW No provenance attestation provenance

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

v1.14.0

1 finding
LOW No provenance attestation provenance

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

v1.13.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.