@improbable-eng/grpc-web

gRPC-Web client for browsers (JS/TS)

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

jonnyreevesmarcuslongmuir

Keywords

grpcgrpc-webprotobuftypescriptts

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from jonnyreeves to marcuslongmuir reflects a legitimate internal transition at Improbable Engineering; marcuslongmuir has a long, clean track record (11 approved packages, 3341 days on npm).	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): marcuslongmuir is a long-standing npm user with a clean record; addition is consistent with a legitimate org-internal maintainer transition.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Established package from a known org; missing gitHead reflects a publish environment change, not a security threat. No other corroborating malicious signals.	ai	2026/04/23

Versions (showing 14 of 14)

Version	Deps	Published
0.15.0	1 / 7	2021-11-04
0.14.1	1 / 7	2021-08-23
0.14.0	1 / 7	2021-02-05
0.13.0	1 / 7	2020-07-15
0.12.0	1 / 7	2019-12-13
0.11.0	1 / 7	2019-08-06
0.10.0	1 / 7	2019-08-05
0.9.6	1 / 7	2019-06-03
0.9.5	1 / 7	2019-05-07
0.9.4	1 / 7	2019-05-07
0.9.3	1 / 7	2019-05-07
0.9.2	1 / 7	2019-05-03
0.9.1	1 / 7	2019-02-26
0.8.0	1 / 6	2019-01-10

v0.15.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marcuslongmuir.

LOW No provenance attestation provenance

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

v0.14.1

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marcuslongmuir.

v0.14.0

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marcuslongmuir.

v0.13.0

3 findings

HIGH Publisher changed: jonnyreeves → marcuslongmuir (on 2020-07-15) provenance

This version was published by a different npm account than previous versions on 2020-07-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marcuslongmuir.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.5

1 finding

LOW No provenance attestation provenance

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

v0.9.4

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.