← Home

@testflowkit/cli

npm Repository Homepage

TestFlowKit CLI - A powerful end-to-end testing framework using Gherkin syntax

13
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

marckent04dreamsfollowers

Keywords

testflowkittestinge2eend-to-endgherkincucumberbddcliautomation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): CLI tool spawning subprocesses via child_process is expected and documented behavior. ai
install-scripts install-script:postinstall AI (install-scripts): CLI tool uses postinstall for setup/binary download via adm-zip; consistent with package purpose across versions. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @testflowkit/cli is unrelated to joi; Levenshtein match is a false positive on the scoped suffix. ai

Versions (showing 13 of 13)

Version Deps Published
3.9.0 0 / 0
3.8.0 0 / 0
3.7.0 0 / 0
3.6.1 0 / 0
3.6.0 0 / 0
3.5.2 0 / 0
3.5.1 0 / 0
3.5.0 0 / 0
3.4.0 0 / 0
3.3.0 0 / 0
3.2.0 1 / 0
2.1.0 1 / 0
2.0.0 1 / 0

v3.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding
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.

v3.4.0

1 finding
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.

v3.3.0

1 finding
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.

v3.2.0

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

Script: node -e "process.env.CI || require('./lib/install.js')"

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.

v2.1.0

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

Script: node ./lib/install.js

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.

v2.0.0

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

Script: node ./lib/install.js

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.