yeswedev/custom-content-manager

Release historydanger

This is the package's only release, published 658 days ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with a project that has been inactive since its initial release. No provided signal compensates for this maintenance gap.

Licensecaution

Neither the package metadata nor the artifact or repository contains a recognized license or license file. This creates a concrete transparency and reuse risk for a package intended to be consumed as a dependency.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package. Although name differences can occur in monorepos, these combined values weaken confidence that the repository clearly represents this package.

Security policycaution

The linked repository has no security policy. This is a maintenance and disclosure gap, though it is less significant than the lack of release and commit activity.