@hestia-earth/api
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:passport-gitlab2 | AI (phantom-deps): Used as a Passport strategy configured at runtime, not directly imported in source files. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'hapi' is a false positive across all versions. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'ajv' is a false positive. | ai | |
| phantom-deps | phantom-dep:@hestia-earth/json-schema | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for type-only or indirect usage patterns. | ai |
Versions (showing 90 of 190)
| Version | Deps | Published |
|---|---|---|
| 0.25.32 | 4 / 83 | |
| 0.25.31 | 4 / 83 | |
| 0.25.30 | 4 / 83 | |
| 0.25.29 | 4 / 83 | |
| 0.25.28 | 4 / 83 | |
| 0.25.27 | 4 / 83 | |
| 0.25.26 | 4 / 83 | |
| 0.25.25 | 4 / 83 | |
| 0.25.24 | 4 / 83 | |
| 0.25.23 | 4 / 83 | |
| 0.25.22 | 4 / 83 | |
| 0.25.21 | 4 / 83 | |
| 0.25.20 | 4 / 83 | |
| 0.25.19 | 4 / 83 | |
| 0.25.18 | 4 / 83 | |
| 0.25.17 | 4 / 83 | |
| 0.25.16 | 4 / 83 | |
| 0.25.15 | 4 / 83 | |
| 0.25.14 | 4 / 83 | |
| 0.25.13 | 3 / 83 | |
| 0.25.12 | 3 / 83 | |
| 0.25.11 | 3 / 83 | |
| 0.25.10 | 3 / 83 | |
| 0.25.9 | 3 / 84 | |
| 0.25.8 | 3 / 84 | |
| 0.25.7 | 3 / 84 | |
| 0.25.6 | 3 / 84 | |
| 0.25.5 | 3 / 84 | |
| 0.25.4 | 3 / 84 | |
| 0.25.3 | 3 / 84 | |
| 0.25.2 | 3 / 84 | |
| 0.25.1 | 3 / 84 | |
| 0.25.0 | 3 / 84 | |
| 0.24.82 | 3 / 84 | |
| 0.24.81 | 3 / 84 | |
| 0.24.80 | 3 / 84 | |
| 0.24.79 | 3 / 84 | |
| 0.24.78 | 3 / 84 | |
| 0.24.77 | 3 / 84 | |
| 0.24.76 | 3 / 84 | |
| 0.24.75 | 3 / 84 | |
| 0.24.74 | 3 / 84 | |
| 0.24.73 | 3 / 84 | |
| 0.24.72 | 3 / 84 | |
| 0.24.71 | 3 / 84 | |
| 0.24.70 | 3 / 84 | |
| 0.24.69 | 3 / 84 | |
| 0.24.68 | 3 / 84 | |
| 0.24.67 | 3 / 84 | |
| 0.24.66 | 3 / 84 | |
| 0.24.65 | 3 / 84 | |
| 0.24.64 | 3 / 84 | |
| 0.24.63 | 3 / 84 | |
| 0.24.62 | 3 / 84 | |
| 0.24.61 | 3 / 84 | |
| 0.24.60 | 3 / 84 | |
| 0.24.59 | 3 / 84 | |
| 0.24.58 | 3 / 84 | |
| 0.24.57 | 3 / 84 | |
| 0.24.56 | 3 / 84 | |
| 0.24.55 | 3 / 84 | |
| 0.24.54 | 3 / 84 | |
| 0.24.53 | 3 / 84 | |
| 0.24.52 | 3 / 84 | |
| 0.24.51 | 3 / 84 | |
| 0.24.50 | 3 / 84 | |
| 0.24.49 | 3 / 84 | |
| 0.24.48 | 3 / 84 | |
| 0.24.47 | 3 / 84 | |
| 0.24.46 | 3 / 84 | |
| 0.24.45 | 3 / 84 | |
| 0.24.44 | 3 / 84 | |
| 0.24.43 | 3 / 84 | |
| 0.24.42 | 3 / 84 | |
| 0.24.41 | 3 / 84 | |
| 0.24.40 | 3 / 84 | |
| 0.24.39 | 3 / 84 | |
| 0.24.38 | 3 / 84 | |
| 0.24.37 | 3 / 84 | |
| 0.24.36 | 3 / 84 | |
| 0.24.35 | 3 / 84 | |
| 0.24.34 | 3 / 84 | |
| 0.24.33 | 3 / 84 | |
| 0.24.32 | 3 / 84 | |
| 0.24.31 | 3 / 84 | |
| 0.24.30 | 3 / 84 | |
| 0.24.29 | 3 / 84 | |
| 0.24.28 | 3 / 84 | |
| 0.24.27 | 3 / 82 | |
| 0.24.26 | 3 / 82 |
v0.24.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.