milpa/events

Maintainerscaution

Only one registry account has publish access, which is a publishing continuity concern, though the linked repository is owned by an organization and the repository shows active maintenance.

Repo bus factorcaution

One contributor made 100% of the 17 recent commits, creating a genuine continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This is weak supporting evidence, but popularity is not decisive for a young, specialized package.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected; the missing scanning reduces security-process transparency without indicating abandonment.

Token permissionscaution

All workflows declare top-level permissions, but three of four grant top-level write permissions; this is broader automation authority than ideal and warrants review.