yoanbernabeu/daplos-bundle

Maintainerscaution

Only one registry account can publish releases, which creates continuity risk for a user-owned project even though repository activity is current.

Project backingcaution

The registry namespace and repository belong to the same individual user, confirming project ownership but offering no organizational maintenance redundancy.

Repo bus factorcaution

One contributor made all four commits in the last 3 months, leaving the project highly dependent on a single person and increasing abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a transparency and maintenance gap for dependency security.

Security policycaution

The repository has no security policy, so users lack documented guidance for reporting vulnerabilities or handling security issues.