msbios/content

Release historydanger

The package has made no release in more than seven years, with zero releases in the last 12 months. Four total releases show an established history but do not offset the prolonged inactivity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and increasing abandonment risk.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package, so ownership of the published artifact is not clearly established.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces assurance without independently making the release unfit.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a transparency gap, though it is less serious than the maintenance concerns.