Package Health/bright-cloud-studio/contao_redirects

bright-cloud-studio/contao_redirects

The package has a small dependency surface and a usable README, but its declared LGPL-3.0+ differs from the bundled GPL-3.0 license. No security policy or automated security scanning is present, so verify licensing before adoption.

Latest 1.0.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

The manifest declares LGPL-3.0+, while the bundled LICENSE file is detected as GPL-3.0. The release is licensed, but the mismatch creates a meaningful licensing ambiguity.

Package file tree

The package artifact contains the implementation and configuration files, but the linked repository exposes only README.md and composer.json. That separation weakens transparency about the source used to produce the release.

Release history

The package has three releases, all published on the same day, with no later release activity over about six months. This provides limited evidence of an established maintenance cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. For a package only about six months old, that is a meaningful warning about maintenance continuity.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a modest repository-hygiene concern rather than evidence of unsafe code.