← Home

@hestia-earth/bulk-api

npm Repository Homepage

Hestia Download API definitions

48
Versions
UNLICENSED
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

mebibou

Keywords

hestiadownloaddataapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:UNLICENSED AI (license): Intentionally proprietary package; UNLICENSED is consistent across all versions of this package. ai
provenance no-provenance AI (provenance): Hestia Earth org consistently publishes without Sigstore provenance; stable pattern across versions. ai

Versions (showing 48 of 48)

Version Deps Published
0.1.4 2 / 6
0.1.3 2 / 6
0.1.2 2 / 6
0.1.1 2 / 6
0.1.0 2 / 6
0.0.51 2 / 6
0.0.50 2 / 6
0.0.49 2 / 6
0.0.48 2 / 6
0.0.47 2 / 6
0.0.46 2 / 6
0.0.45 2 / 6
0.0.44 2 / 6
0.0.43 2 / 6
0.0.42 2 / 6
0.0.41 2 / 6
0.0.40 2 / 6
0.0.39 2 / 6
0.0.38 2 / 6
0.0.37 2 / 6
0.0.36 2 / 6
0.0.35 2 / 6
0.0.34 2 / 6
0.0.33 2 / 6
0.0.32 2 / 6
0.0.31 2 / 6
0.0.30 2 / 6
0.0.29 2 / 6
0.0.28 2 / 6
0.0.27 2 / 6
0.0.26 2 / 6
0.0.25 2 / 6
0.0.24 2 / 6
0.0.23 2 / 6
0.0.22 2 / 6
0.0.21 2 / 6
0.0.20 2 / 6
0.0.19 2 / 6
0.0.18 2 / 6
0.0.17 2 / 6
0.0.16 2 / 6
0.0.15 2 / 6
0.0.14 2 / 6
0.0.13 2 / 6
0.0.12 2 / 6
0.0.11 2 / 6
0.0.10 2 / 6
0.0.9 2 / 6

v0.1.4

1 finding
INFO No provenance attestation provenance

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

v0.1.3

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

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

v0.0.51

1 finding
INFO No provenance attestation provenance

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

v0.0.50

1 finding
INFO No provenance attestation provenance

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

v0.0.49

1 finding
INFO No provenance attestation provenance

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

v0.0.48

1 finding
INFO No provenance attestation provenance

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

v0.0.13

1 finding
INFO No provenance attestation provenance

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

v0.0.12

1 finding
INFO No provenance attestation provenance

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

v0.0.11

1 finding
INFO No provenance attestation provenance

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

v0.0.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.