ts-debounce

Build provenancecaution

No build attestation or trusted-publisher provenance is present. This weakens publication transparency, though it does not by itself indicate an unhealthy project.

Maintainerscaution

Only one registry account has publishing access. That is a meaningful concentration risk for continuity, although the repository and release history show the project is still active.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. A recent release provides some compensation, but the current source-change activity is thin.

Repo toolingcaution

The repository uses TypeScript and a build tool, but no security-scanning tools were detected. Build tooling is present, while security-process visibility is limited.

Security policycaution

No security policy was found in the repository. This is a transparency gap for reporting and handling vulnerabilities.