CLI for Jasmine, a simple JavaScript testing framework for browsers and Node
82%
Total Score
67
100
95
88
50
No build attestation, trusted publisher, or staged publishing is present, leaving publication origin less verifiable even though this is a transparency gap rather than evidence of abandonment.
One contributor made 100% of the 12 recent commits, creating concentration risk; organization ownership provides some capacity to hand maintenance to another contributor.
The repository recorded 12 commits in the last three months, showing ongoing work, but all came from one active maintainer.
No build tool or security scanning tool was detected, reducing evidence of automated build and security hygiene for the project.
The repository has no security policy, so users have no documented vulnerability-reporting process visible in the collected evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
glob Version ^10.2.2 || ^11.0.3 || ^12.0.0 || ^13.0.0 | — | — |
jasmine-core Version ~7.0.0 | — | — |
@jasminejs/reporters Version ^1.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.