zems/zems_restaurant

Release historydanger

The package has had only two releases, both published nearly three years ago, with no release in the last 12 months. This is strong evidence of abandonment for a library dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No newer activity is provided to offset this concern.

Maintainerscaution

Only one registry account has publish access. The repository is owned by a user rather than an organization, so there is no provided backing evidence to offset the thin maintainer base.

Package file treecaution

The artifact and repository each contain only six files, including two source files and a very short README. This may be a deliberately small package, but it provides little visible implementation or documentation context.

Repo package mentioncaution

The repository name does not match the package name, and its README does not mention the package. That makes package ownership and provenance less transparent, beyond an ordinary monorepo naming difference.