use-debounce

Build provenancecaution

The release has no build attestation, trusted publisher identity, or staged publishing, leaving publication origin and reproducibility less transparent.

Maintainerscaution

Only one account has registry publishing access, creating a limited publishing base; the user-owned repository and mature release history provide some context but do not remove the single-publisher risk.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, which is a meaningful maintenance concern, although recent releases and a repository push provide some compensating evidence.

Repo toolingcaution

The repository uses TypeScript, Microbundle, and npm scripts for builds, but no security-scanning tool was detected, leaving a modest security-hygiene gap.

Security policycaution

No SECURITY policy was found in the repository, reducing transparency about vulnerability reporting and maintainer response procedures.