@smartbear/mcp MIT 39 versions

@smartbear/mcp

npm Repository Homepage

MCP server for interacting SmartBear Products

39

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

smartbear_devopsjonathanparrilla-smartbearpawel.turylamrunkle-sb

Keywords

smartbearmcpbugsnagreflectswaggerpactflowzephyrqtm4j

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): SmartBear org package; maintainer rotation within the org is expected across versions.	ai	2026/05/11
maintainer-change	maintainer-removed	AI (maintainer-change): SmartBear org package; maintainer rotation within the org is expected across versions.	ai	2026/05/11
source-diff	large-new-source-files	AI (source-diff): Active development; new files align with added integrations (bugsnag, pactflow, api-hub) per package keywords.	ai	2026/05/11
source-diff	source-size-tripled	AI (source-diff): Size increase consistent with new feature modules; no obfuscation or bundled payloads indicated.	ai	2026/05/11
publish-pattern	new-deps-added	AI (publish-pattern): zod is a well-established, widely-used validation library with no known malicious history; low risk for this package.	ai	2026/05/11
phantom-deps	phantom-dep:vite	AI (phantom-deps): vite is listed as a runtime dependency and used as a build tool; phantom-dep heuristic misfires here.	ai	2026/04/29
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped SmartBear package; Levenshtein match to 'yup' is coincidental, not a typosquat.	ai	2026/04/29

Versions (showing 39 of 39)

Version	Deps	Published
0.25.0	7 / 10	2026-06-03
0.24.0	7 / 10	2026-05-28
0.23.0	7 / 10	2026-05-22
0.22.0	7 / 10	2026-05-21
0.21.1	7 / 10	2026-05-20
0.20.0	7 / 10	2026-05-15
0.19.2	7 / 10	2026-05-05
0.19.0	7 / 10	2026-04-29
0.18.3	7 / 10	2026-04-20
0.18.2	7 / 10	2026-04-15
0.18.1	7 / 10	2026-04-13
0.18.0	7 / 10	2026-04-13
0.17.1	7 / 10	2026-04-10
0.17.0	7 / 10	2026-04-07
0.16.0	7 / 10	2026-03-26
0.15.0	6 / 9	2026-03-18
0.14.1	6 / 9	2026-02-27
0.14.0	6 / 9	2026-02-26
0.13.5	6 / 9	2026-02-02
0.13.4	6 / 9	2026-01-28
0.13.3	6 / 9	2026-01-21
0.13.2	6 / 9	2026-01-13
0.13.1	6 / 9	2026-01-13
0.12.1	6 / 9	2025-12-09
0.12.0	6 / 9	2025-12-03
0.11.0	6 / 9	2025-11-20
0.10.0	6 / 9	2025-11-11
0.9.0	6 / 9	2025-10-22
0.8.0	6 / 9	2025-10-13
0.7.0	6 / 9	2025-10-02
0.6.0	6 / 11	2025-09-22
0.5.0	5 / 11	2025-09-08
0.4.0	4 / 9	2025-08-27
0.3.0	4 / 9	2025-08-11
0.2.2	3 / 7	2025-07-11
0.2.1	3 / 7	2025-07-09
0.2.0	3 / 7	2025-07-08
0.1.1	2 / 7	2025-07-01
0.1.0	2 / 7	2025-06-27

v0.25.0

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.1

1 finding

LOW No provenance attestation provenance

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

v0.20.0

1 finding

LOW No provenance attestation provenance

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

v0.19.2

1 finding

LOW No provenance attestation provenance

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

v0.18.3

1 finding

LOW No provenance attestation provenance

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

v0.18.2

1 finding

LOW No provenance attestation provenance

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

v0.18.1

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.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.

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.5

1 finding

LOW No provenance attestation provenance

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

v0.13.4

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.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.

v0.10.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.

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

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.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.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

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.2.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.

v0.1.1

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