asar/asar-fs

Release historydanger

Only two releases exist, and the latest was published in May 2014; there have been no releases in more than 12 years. This is strong evidence of an unmaintained dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, against a last release in 2014. This indicates sustained abandonment risk rather than a temporary slowdown.

Licensecaution

The artifact contains a license file, but it is identified as BSD-3-Clause while the manifest declares MIT. The package is licensed, yet the mismatch creates a transparency concern that should be resolved.

Project backingcaution

The package is maintained under a personal repository rather than an organization-owned project. This provides no demonstrated organizational backing to compensate for the inactive history.

Repo popularitycaution

The repository has one star, zero forks, and one watcher. Low adoption is supporting evidence of limited project maturity, though it is not decisive by itself.