boost/craft-structure-plus

Release historydanger

Only two releases are reported, both from the initial release period, with no release in the last 12 months and about 23 months since the latest release. This materially raises abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the long release gap, this is a meaningful maintenance concern.

Project backingcaution

The repository is owned by an individual user rather than an organization, so the limited observable project backing provides little redundancy for maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap, not evidence of unsafe code by itself.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a hygiene gap that adds some maintenance risk.