← Home

@hestia-earth/data-api

npm Repository Homepage

Hestia Data API definitions

79
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

hestiadataapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Internal org package on GitLab; provenance attestation not expected for this publisher pattern. ai
dependencies unvetted-dep:@hestia-earth/schema AI (dependencies): Same-org sibling dependency; stable pattern across all hestia-earth packages. ai

Versions (showing 79 of 79)

Version Deps Published
0.2.4 1 / 69
0.2.3 1 / 69
0.2.2 1 / 69
0.2.1 1 / 69
0.2.0 1 / 69
0.1.26 1 / 69
0.1.25 1 / 69
0.1.24 1 / 69
0.1.23 1 / 68
0.1.22 1 / 68
0.1.21 1 / 68
0.1.20 1 / 68
0.1.19 1 / 68
0.1.18 1 / 68
0.1.17 1 / 68
0.1.16 1 / 68
0.1.15 1 / 68
0.1.14 1 / 68
0.1.13 1 / 68
0.1.12 1 / 68
0.1.11 1 / 68
0.1.10 1 / 68
0.1.9 1 / 68
0.1.8 1 / 68
0.1.7 1 / 68
0.1.6 1 / 72
0.1.5 1 / 72
0.1.4 1 / 72
0.1.3 1 / 72
0.1.2 1 / 72
0.1.1 1 / 72
0.1.0 1 / 72
0.0.63 1 / 72
0.0.62 1 / 72
0.0.61 1 / 72
0.0.60 1 / 72
0.0.59 1 / 72
0.0.58 1 / 72
0.0.57 1 / 72
0.0.56 1 / 72
0.0.55 1 / 72
0.0.54 1 / 72
0.0.53 1 / 72
0.0.52 1 / 72
0.0.51 1 / 72
0.0.50 1 / 72
0.0.49 1 / 72
0.0.48 1 / 72
0.0.47 1 / 72
0.0.46 1 / 72
0.0.45 1 / 72
0.0.44 1 / 72
0.0.43 1 / 72
0.0.42 1 / 70
0.0.41 2 / 67
0.0.40 2 / 67
0.0.39 2 / 66
0.0.38 2 / 65
0.0.37 2 / 65
0.0.36 2 / 65
0.0.35 2 / 65
0.0.34 2 / 65
0.0.33 2 / 65
0.0.32 2 / 65
0.0.31 2 / 65
0.0.30 1 / 64
0.0.29 1 / 64
0.0.28 1 / 64
0.0.27 1 / 64
0.0.26 1 / 64
0.0.25 1 / 64
0.0.24 1 / 64
0.0.23 1 / 64
0.0.22 1 / 64
0.0.21 1 / 64
0.0.20 1 / 64
0.0.19 1 / 64
0.0.18 1 / 64
0.0.17 1 / 64

v0.2.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.2.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.0.38

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.37

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.36

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.35

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.34

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.33

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.32

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.31

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.30

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.29

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.28

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.27

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.26

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.25

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.24

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.23

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.22

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.21

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.20

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.19

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.18

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.17

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.