Display differences clearly so people can review changes confidently.
88%
Total Score
88
100
89
83
One contributor made about 96% of the 73 recent commits, leaving a meaningful concentration risk; organization backing partly compensates because maintenance can be handed off within the project.
The repository name does not match jest-diff and its README does not mention the package, which creates some package-to-repository transparency concern; the Jest organization and monorepo context partly compensate for the name mismatch.
The repository uses established build tools and has a build system, but no security scanning tools were detected, leaving a modest security-hygiene gap.
All 11 workflows were analyzed successfully; all 48 action references are pinned and no untrusted checkout or script-injection sink was found. The high-confidence trusted-publishing finding is an audit caution, while the pull_request_target trigger has no demonstrated sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chalk Version ^4.1.2 | — | — |
pretty-format Version 30.5.1 | — | — |
@jest/get-type Version 30.5.0 | — | — |
@jest/diff-sequences Version 30.5.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.