@smartbear/one-report-publisher MIT 17 versions

@smartbear/one-report-publisher

npm Repository Homepage

Publish Test Results to SmartBear OneReport

17

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

severine.darlotkaram.elhaboutiaslakhellesoymarverixvincent-psargavincentcapicottojbprostimotheevilleaurelien.reevesmcoqblin-smartbearn-murphysmartbear_devopscbonromaingweb

Keywords

cucumberstepsregexpregex

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): Vendored commander code in bundled CLI, not injected payload.	ai	2026/07/27
semgrep	semgrep:child-process-spawn	AI (semgrep): Commander's built-in executableSubcommand spawn logic, dual-use and expected.	ai	2026/07/27
source-diff	source-size-tripled	AI (source-diff): New bundled CLI entrypoint (build:cli/esbuild) accounts for size increase.	ai	2026/07/27
phantom-deps	phantom-dep:@types/adm-zip	AI (phantom-deps): @types/adm-zip is a TypeScript type declaration; not directly imported at runtime by design.	ai	2026/04/29

Versions (showing 17 of 17)

Version	Deps	Published
0.8.0	6 / 20	2022-08-16
0.7.0	6 / 20	2022-07-12
0.6.0	6 / 20	2022-07-05
0.5.0	6 / 20	2022-06-29
0.4.0	6 / 20	2022-06-22
0.3.2	6 / 20	2022-03-04
0.3.1	6 / 20	2022-03-04
0.3.0	6 / 20	2022-02-09
0.2.0	6 / 20	2022-02-07
0.1.0	6 / 20	2022-01-31
0.0.14	4 / 20	2022-01-27
0.0.13	4 / 20	2022-01-27
0.0.12	3 / 20	2022-01-26
0.0.11	3 / 20	2022-01-26
0.0.10	2 / 20	2022-01-26
0.0.9	2 / 20	2022-01-26
0.0.8	2 / 20	2022-01-26

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

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.

v0.0.8

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.