blackcube/dcore

Release historycaution

This is a very new package, with one release published 16 days ago and no established release cadence. That limits evidence of long-term maintenance.

Repo bus factorcaution

One contributor made all two recent commits, creating a concentrated maintenance dependency. Organization ownership offers some handoff capacity, but no second active contributor is shown.

Repo commit activitycaution

Only two commits were recorded in the last three months, so there is limited evidence of sustained maintenance beyond the initial release.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a maintenance and hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a database-facing library.