jzh/jwt

Release historydanger

The package has had no releases in the last four years, despite seven releases overall, which is a substantial abandonment concern for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the release history showing that development stopped over four years ago.

Dependency profilecaution

The package has three runtime dependencies and no development dependencies. This is a manageable runtime footprint, though the absence of development dependencies gives limited visibility into how the package is tested.

Project backingcaution

The package and repository are associated with the same individual account rather than an organization, so there is no evident organizational backing to compensate for the thin maintenance record.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, indicating little visible adoption or external review. Popularity is supporting evidence, but this reinforces the maintenance concern.