pkg-up

Registry deprecationdanger

The entire package is deprecated with the explicit message “Renamed to package-up,” so new consumers should use the replacement name instead. This is a severe adoption and maintenance risk for this release.

Project backingcaution

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it offers less institutional continuity to compensate for the package’s deprecation and inactive recent commit period.

Release historycaution

The package has seven releases since 2015, but no releases in the last 12 months and its latest registry release was nearly three years ago. The repository was pushed more recently, which provides some compensating evidence but does not restore the old package’s release path.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Although the recent repository push is somewhat reassuring, the current activity snapshot gives little evidence of ongoing maintenance.

Repo toolingcaution

No build tools or security scanning tools were detected in the repository. For this small JavaScript utility this is a hygiene gap rather than evidence that the package is unusable.