imagewize/simple-cookie-consent

Registry deprecationdanger

Packagist marks the entire package as abandoned and names imagewize/warder-cookie-consent as its replacement. Package-level deprecation is a severe dependency-maintenance risk even though the assessed release itself is current.

Repo package mentioncaution

The repository name does not match this package and its README does not mention the package, so the linkage is not transparent. This is especially relevant because the registry identifies this package as replaced by that repository’s package.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a security-process gap, though the active repository and clean workflow analysis provide some compensating evidence.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response guidance undocumented. This is a transparency gap for a package that handles website consent behavior.

Token permissionscaution

All three workflows lack top-level token-permission declarations, so their GitHub Actions permissions are not explicitly minimized. No workflow requests top-level write access, which limits the practical concern.