@improbable-eng/grpc-web-node-http-transport
Node HTTP Transport for use with @improbable-eng/grpc-web
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): marcuslongmuir is a long-standing npm account (3341 days) within the @improbable-eng org; this is a legitimate maintainer transition, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is an established account within the same org scope; transition is consistent with normal org contributor management. | ai | |
| provenance | missing-githead | AI (provenance): Established package from trusted Improbable org publisher; missing gitHead is a publish-environment change, not a security indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a process gap, not a security risk for this well-established package from a trusted publisher. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 0 / 4 | |
| 0.14.1 | 0 / 4 | |
| 0.14.0 | 0 / 4 | |
| 0.13.0 | 0 / 4 | |
| 0.12.0 | 0 / 4 | |
| 0.11.0 | 0 / 4 | |
| 0.10.0 | 0 / 4 | |
| 0.9.6 | 0 / 4 | |
| 0.9.5 | 0 / 4 | |
| 0.9.2 | 0 / 4 | |
| 0.9.1 | 0 / 4 | |
| 0.0.2 | 0 / 4 |
v0.15.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marcuslongmuir.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.