@visx/responsive

Repo bus factorcaution

One contributor made about 82% of the recent commits, creating concentration risk, though two other contributors remained active and the repository is organization-owned.

Repo issue activitycaution

Only one issue was opened and no pull requests were merged in the last month, despite two new pull requests; this is a modest sign of slower review activity, not abandonment given the recent release and commits.

Repo package mentioncaution

The repository name does not match the package and its README does not mention @visx/responsive, so the package-to-repository link is less transparent than ideal despite the monorepo file tree containing related package content.

Repo toolingcaution

The project uses TypeScript, Vitest, Babel, and npm scripts, but no security scanning tools were detected; this is a modest process gap rather than evidence of abandonment.

Workflow auditcaution

Both workflows were fully analyzed with no dangerous triggers, untrusted checkouts, script injections, or audit findings; however, all six action references are unpinned, which weakens build reproducibility.