beautystack/database-contracts

Release historydanger

The package has had no releases in the last 12 months, and its latest release was about four years ago. This is strong evidence of abandonment risk for a dependency that may need compatibility fixes.

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 that concern.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so ownership of the published package is less transparent. A monorepo can explain a name mismatch, but the missing README mention leaves a genuine gap.

Repo toolingcaution

The project uses Composer and Make for build tasks, showing basic build structure. No security scanning tooling is present, which is a modest hygiene gap but not decisive for this small package.

Security policycaution

The repository has no security policy, reducing transparency about how maintainers handle vulnerability reports. This is a minor concern rather than evidence that the package is unsafe.