← Home

hive-uri

npm

Hive URI parser and encoder

10
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

feruzmesteem.app

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): atob polyfill for Node.js; expected in a URI parser handling base64 data, not a malicious payload. ai

Versions (showing 10 of 10)

Version Deps Published
0.2.8 1 / 5
0.2.7 0 / 5
0.2.6 0 / 5
0.2.5 0 / 4
0.2.4 0 / 4
0.2.3 0 / 4
0.2.2 0 / 4
0.2.1 0 / 4
0.2.0 0 / 4
0.1.0 0 / 4

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

2 findings
MEDIUM Publisher changed: esteem.app → feruzm (on 2021-02-18, unremoved on npm for 1983d) provenance

This version was published by a different npm account (feruzm) than the most recent previously approved version (esteem.app) on 2021-02-18. It has since remained available on npm for 1983 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.

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