public-encrypt

Build provenancecaution

No build attestation or trusted-publisher provenance is available for the release, so consumers have less evidence connecting the published artifact to its source. This lowers supply-chain transparency but is not by itself evidence that the package is unsafe.

Release historycaution

The latest release was published nearly eight years ago, and there were no releases in the last 12 months. This is a meaningful freshness and maintenance concern, despite the package having 11 releases and a stable release history earlier in its life.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last three months. Although the repository was pushed more recently than the package release, current development activity is not evident.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That makes the source relationship less transparent, even though the naming difference could reflect a related project layout.

Type declarationscaution

No type declarations are provided, which makes integration less convenient for typed consumers. This is a consumer-ergonomics gap rather than a severe maintenance risk.