tulparcms/cms

Repo commit activitydanger

There have been zero commits and zero active maintainers in the last 3 months. Together with the single historical release, this indicates a substantial abandonment risk.

Maintainerscaution

Only one registry account has publish access. That is a limited publishing base and increases continuity risk when combined with the absence of recent activity.

Package scaffoldingcaution

A changelog and GitHub release are present, but the published README contains only one character, giving consumers almost no usage documentation. The absence of published tests is normal packaging practice.

Release historycaution

The package has only one release, published about 2 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of limited ongoing maintenance.

Repo issue activitycaution

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a quiet project, though it does not by itself prove abandonment.