@dnd-kit/accessibility

Project backingcaution

The repository is owned by an individual rather than an organization, so the single registry maintainer provides limited administrative redundancy. Recent activity from six repository contributors partly offsets that concern.

Release historycaution

There have been no registry releases in nearly two years, which raises freshness concerns for consumers. Recent repository activity partly compensates by showing that the project itself is still maintained.

Repo toolingcaution

The project uses established build tooling, but no repository security-scanning tools were detected. This is a modest transparency and maintenance gap.

Security policycaution

No security policy was found in the repository, leaving vulnerability-reporting expectations unclear. This is a hygiene gap rather than evidence of unsafe code.

Workflow auditcaution

All five workflows were analyzed and use read-only permissions, with no untrusted checkouts or script injection findings. However, 29 of 33 action references are unpinned and the release workflow installs a package outside a lockfile, creating avoidable build-reproducibility risk.