find-replace

Build provenancecaution

No build attestation or trusted-publisher identity is present. This reduces release transparency, though it is a supply-chain hygiene gap rather than evidence that the package is unsafe.

Maintainerscaution

Only one registry account has publish access, and the repository owner is an individual rather than an organization. That creates limited publishing and ownership redundancy, especially alongside the inactive recent history.

Release historycaution

The package has 16 releases since July 2015, but none in the last 12 months and the latest release was about two years ago. This suggests a mature, possibly stable utility, but also leaves current maintenance uncertain.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being about two years ago. This is the strongest maintenance concern for a dependency.

Repo toolingcaution

The repository uses Rollup and npm scripts, showing an established build process, but no security scanning tools were detected. The build setup is positive while security-tooling coverage is limited.