append-buffer

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old registry release history, this indicates weak ongoing maintenance capacity.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, so registry consumers have limited evidence connecting this artifact to its source build. This is a transparency gap, but not severe on its own.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to compensate for the thin maintenance activity.

Release historycaution

The package has three releases, all published within a short period in August 2017, and none in the last 12 months. This is meaningful evidence of a long-standing release gap, although the package may be functionally stable.

Repo popularitycaution

The repository has 10 stars and one fork, indicating a small user and contributor footprint. Low popularity is supporting evidence only and is partly offset by the package's narrow scope.