A better path.resolve() that normalizes paths on Windows
68%
Total Score
50
100
83
67
50
No build attestation or trusted-publisher configuration is present, reducing publication transparency; this is a supply-chain hygiene gap rather than evidence that the release is unsafe.
Only one registry account has publish access. That is a limited publishing base, although repository activity provides some additional evidence of ongoing ownership.
The package has only two releases across roughly seven and a half years, with one release in the last 12 months. The recent release shows current activity, but the long interval indicates a mature, very slow-moving project.
All two recent commits came from one contributor, leaving maintenance dependent on a single active developer.
The repository recorded two commits in the last three months, so it is active but only lightly maintained.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
is-windows Version ^1.0.2 | — | — |
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.