@repeaterjs/repeater

Build provenancecaution

No build attestation or trusted publisher information is provided, leaving publication provenance less transparent even though the package has a matching active repository and documented release.

Repo toolingcaution

The repository uses TypeScript and npm build tooling, providing a defined build process, but it has no security scanning tools, which leaves a modest security-hygiene gap.

Security policycaution

The repository has no published security policy, making vulnerability reporting and response expectations less transparent for users.

Token permissionscaution

The only workflow lacks top-level token permissions, so its intended access is not explicitly constrained even though no top-level write permission was observed.