visx point
70%
Total Score
caution
Usable with caveats: recent repository activity is concentrated in one commit, and all workflow actions are unpinned.
All recent commit activity came from one contributor, creating concentration risk. Organization backing partly compensates because maintenance can potentially be handed off.
Only one commit was recorded in the last three months, indicating very limited recent source activity. This is a meaningful maintenance concern even though the package released 13 times in the prior year.
The repository had one new issue and two new pull requests in the last month but merged none, which is weak evidence of current responsiveness. The short observation window limits how strongly this should weigh.
The repository name does not match @visx/point and its README does not mention the package. Although name mismatches are normal for monorepos, the absence of both signals creates uncertainty about package-to-repository alignment.
Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injections, or audit findings, and one scopes permissions at job level. However, all six action references are unpinned, weakening workflow reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.