buffer-alloc-unsafe

Build provenancecaution

No build attestation or trusted-publisher provenance is available, leaving publication origin less transparent. This is a transparency gap, not evidence that the release is unsafe.

Project backingcaution

The repository is owned by an individual user rather than an organization, so the project does not show organizational backing to compensate for its thin maintenance history.

Release historycaution

The package has had 4 releases since August 2016, with no releases in the last 12 months and the latest release in May 2018. This is a substantial maintenance gap, although the package is a small, stable utility.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package's long release hiatus and indicating limited ongoing maintenance.

Repo toolingcaution

The repository uses no build tooling and has no security-scanning tools. For this small JavaScript utility the build gap is minor, but the absence of scanning reduces maintenance transparency.