← Home

cypress

npm Repository Homepage
2
Versions
—
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

cypress-npm-publisherbrian-mann

Keywords

automationbrowsercypresscypress.ioe2eend-to-endintegrationcomponentmocksrunnerspiesstubstesttesting

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:enquirer AI (phantom-deps): Referenced in config; stable pattern for this package. ai
phantom-deps phantom-dep:@types/sizzle AI (phantom-deps): Framework-scoped type package loaded by convention. ai
phantom-deps phantom-dep:@types/sinonjs__fake-timers AI (phantom-deps): Framework-scoped type package loaded by convention. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit runtime dependency. ai
phantom-deps phantom-dep:@types/tmp AI (phantom-deps): Framework-scoped type package loaded by convention. ai
typosquat typosquat.levenshtein:express AI (typosquat): Cypress is an established brand, not a typosquat of express. ai
install-scripts install-script:postinstall AI (install-scripts): Documented binary download step; stable for cypress. ai

Versions (showing 2 of 2)

Version Deps Published
15.14.1 43 / 0
15.13.1 43 / 0

v15.14.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node dist/index.js --exec install

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v15.13.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node dist/index.js --exec install

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.