browserify-cipher

Build provenancecaution

No build attestation or trusted-publisher provenance is available, so consumers cannot verify how this release was produced. This is a transparency gap, though not evidence that the release is unsafe.

Release historycaution

The package has only two releases, with none in the last 12 months; its latest release was published over eight years ago. This is a substantial maintenance concern despite the repository still existing.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long gap since the latest registry release, this weakens confidence in ongoing maintenance.

Repo toolingcaution

The repository reports no build tooling and no security scanning. For a small JavaScript package this is not disqualifying, but the absence of scanning reduces maintenance and security-process transparency.

Security policycaution

No security policy is present in the repository, leaving vulnerability-reporting expectations undocumented.