@lukeed/ms

Maintainerscaution

Only one registry maintainer is listed. The repository is user-owned rather than organization-owned, so there is no provided organizational backing to offset the thin maintainer base.

Project backingcaution

The registry namespace and repository are owned by the same individual, and the repository owner is a user rather than an organization. This supports ownership consistency but provides limited evidence of broader project backing.

Release historycaution

Only four releases have been published, with none in the last 12 months; the latest release was nearly three years ago. This is a meaningful maintenance concern for a package with a stable, small scope, but not abandonment by itself.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. For a small stable utility this may reflect completion, but it reduces evidence of ongoing maintenance.

Repo toolingcaution

The repository uses npm build scripts but has no detected security-scanning tools. This is a modest transparency and hygiene gap, not evidence of unsafe code.