vendored packages for visx
70%
Total Score
caution
Usable with caveats: only one repository commit in three months and all six workflow actions are unpinned.
All one recent commit came from a single contributor. The organization-owned repository provides handoff capacity, but no second active contributor is shown in this period.
Only one commit was recorded in the last three months, by one active maintainer. The recent release and organization backing partly compensate, but this is still a meaningful sign of slowing maintenance.
In the last month, one issue was opened and no issues or pull requests were closed or merged. This supports the broader concern about limited recent maintenance activity.
The repository name does not match @visx/vendor and its README does not mention the package, creating uncertainty about the package-to-repository link. The package's README describes its role, but the repository-level mismatch remains a caution.
The repository uses TypeScript, Vitest, Babel, and npm scripts, but no security scanning tools were detected. The development tooling is solid; the missing scanning is a modest transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
d3-geo Version 3.1.0 | — | — |
d3-path Version 3.1.0 | — | — |
d3-time Version 3.1.0 | — | — |
d3-array Version 3.2.1 | — | — |
d3-color Version 3.1.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.