oauthjwtservice/oauth-jwt-service

Project backingcaution

The repository owner is an individual user rather than an organization. That is not inherently unhealthy, but it offers less visible institutional backing for a package with no recent commits.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. This conflicts with the frequent registry releases and raises a meaningful maintenance concern.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. This creates uncertainty about whether the linked repository is the package's authoritative source.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Low popularity is supporting context rather than a verdict, but it provides little evidence of external adoption or review.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are reported. The missing scanning is a hygiene gap rather than evidence of abandonment.