bfg/scaffold

Release historydanger

The package has made no releases in the last 12 months, and its latest release was about four years ago. Its 38-release history shows past activity but does not offset the prolonged current silence.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and raising abandonment risk.

Maintainerscaution

Only one registry account, “bfg,” has publish access. The linked repository is user-owned rather than organization-owned, so this represents a thin visible publishing base.

Project backingcaution

The registry namespace and repository owner are aligned around bfg/bfg-s, and the repository is user-owned. This supports package identity but does not provide organization-level continuity.

Repo issue activitycaution

There were no new issues or pull requests in the last month and no open work, providing no evidence of current maintenance or user support.