← Home

@protobufjs/fetch

npm Repository Homepage

Fetches the contents of a file accross node and browsers.

7
Versions
BSD-3-Clause
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

dcodeprotobufjsgoogle-wombot

Versions (showing 7 of 7)

Version Deps Published
1.1.1 1 / 2
1.1.0 2 / 2
1.0.4 2 / 0
1.0.3 2 / 0
1.0.2 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
MEDIUM Publisher changed: protobufjs → dcode (on 2016-12-12, unremoved on npm for 3505d) provenance

This version was published by a different npm account (dcode) than the most recent previously approved version (protobufjs) on 2016-12-12. It has since remained available on npm for 3505 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.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.