konradmichalik/typo3-mcp-server-content-planner

Lifecycle scriptscaution

A post-install-cmd lifecycle script introduces install-time execution that should be reviewed before depending on the package, even though no dangerous behavior is shown by this signal alone.

Maintainerscaution

Only one registry account has publish access. This is a real publishing continuity risk for a user-owned project, with repository activity showing the same concentration rather than a broader maintainer base.

Project backingcaution

The repository is owned by an individual user rather than an organization, so the single-maintainer and single-contributor concentration is not compensated by visible organizational backing.

Release historycaution

The package is only 26 days old with three releases and a median interval of about 13 days, showing active early development but limited evidence of long-term maintenance.

Repo bus factorcaution

One contributor made 100% of the 48 recent commits, creating a severe concentration risk for continuity; the repository is user-owned, so no organization-level handoff capacity is evidenced.