please-upgrade-node

Release historydanger

The package has 9 releases but none in the last 12 months, and its latest registry release was in August 2019. This is a substantial maintenance concern for a dependency, despite the package's small scope.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. This weakens evidence of active maintenance, even though a later repository push is recorded elsewhere.

Build provenancecaution

No build attestation, trusted publisher, or staged publishing is present, so publication transparency is limited. This is a hygiene gap rather than evidence that the release is unsafe.

Maintainerscaution

Only one registry account has publish access. This is a modest publishing-resilience concern, although the repository evidence shows the package is tied to the same individual owner.

Project backingcaution

The repository is owned by the individual account typicode rather than an organization. This provides less organizational continuity, but the ownership is consistent with the linked project and is not a standalone abandonment finding.