← Home

@radix-ui/react-use-effect-event

npm Repository Homepage

## Usage

4
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

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance for radix-ui org. ai
maintainer-change maintainer-added AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; expected org-level change. ai
maintainer-change maintainer-removed AI (maintainer-change): Individual maintainers replaced by org account; consistent with WorkOS transition. ai
npm-metadata no-description AI (npm-metadata): Internal utility package in radix-ui monorepo; missing description is benign. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Radix UI consistently uses 0.0.0 for new primitives; not indicative of malicious intent for this publisher/org. ai

Versions (showing 4 of 4)

Version Deps Published
0.0.3 1 / 8
0.0.2 1 / 10
0.0.1 1 / 10
0.0.0 1 / 10

v0.0.3

2 findings
HIGH Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06) provenance

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

v0.0.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.

v0.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.