@hestia-earth/api No license 51 versions

@hestia-earth/api

npm Repository Homepage

51

Versions

—

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mebibou

Keywords

hestiaapi

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	2026/05/15
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'hapi' is a false positive across all versions.	ai	2026/05/15
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'pg' is a false positive.	ai	2026/05/15
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'joi' is a false positive.	ai	2026/05/15
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped @hestia-earth org package; Levenshtein match to 'ajv' is a false positive.	ai	2026/05/15
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	2026/05/15

Versions (showing 51 of 87)

View all versions

Version	Deps	Published
0.26.2	3 / 90	2026-06-06
0.26.1	3 / 90	2026-06-05
0.26.0	3 / 90	2026-05-28
0.25.79	3 / 90	2026-05-27
0.25.78	3 / 90	2026-05-27
0.25.77	3 / 90	2026-05-18
0.25.76	3 / 90	2026-05-15
0.25.75	3 / 90	2026-05-15
0.25.74	3 / 90	2026-05-14
0.25.73	3 / 90	2026-05-14
0.25.72	3 / 90	2026-05-13
0.25.71	3 / 90	2026-05-13
0.25.70	3 / 90	2026-05-13
0.25.69	3 / 93	2026-05-08
0.25.68	3 / 93	2026-05-06
0.25.67	3 / 93	2026-05-05
0.25.66	3 / 93	2026-05-05
0.25.65	3 / 93	2026-05-05
0.25.64	3 / 93	2026-05-05
0.25.63	3 / 92	2026-05-04
0.25.62	3 / 92	2026-04-30
0.25.61	3 / 92	2026-04-30
0.25.60	3 / 92	2026-04-29
0.25.59	3 / 92	2026-04-21
0.25.58	3 / 92	2026-04-17
0.25.57	3 / 92	2026-04-16
0.25.56	3 / 92	2026-04-16
0.25.55	3 / 92	2026-04-16
0.25.54	3 / 92	2026-04-10
0.25.53	3 / 92	2026-04-09
0.25.52	3 / 92	2026-04-09
0.25.51	3 / 92	2026-04-09
0.25.50	4 / 89	2026-04-09
0.25.49	4 / 89	2026-03-31
0.25.48	4 / 89	2026-03-26
0.25.47	4 / 89	2026-03-26
0.25.46	4 / 83	2026-03-17
0.25.45	4 / 83	2026-03-15
0.25.44	4 / 83	2026-03-10
0.25.43	4 / 83	2026-02-25
0.25.42	4 / 83	2026-02-23
0.25.41	4 / 83	2026-02-23
0.25.40	4 / 83	2026-02-13
0.25.39	4 / 83	2026-02-13
0.25.38	4 / 83	2026-02-12
0.25.37	4 / 83	2026-02-07
0.25.36	4 / 83	2026-02-06
0.25.35	4 / 83	2026-02-06
0.25.34	4 / 83	2026-02-02
0.25.33	4 / 83	2026-01-31
0.25.32	4 / 83	2026-01-28

v0.26.2

1 finding

LOW No provenance attestation provenance

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

v0.26.1

1 finding

LOW No provenance attestation provenance

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

v0.26.0

1 finding

LOW No provenance attestation provenance

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

v0.25.79

1 finding

LOW No provenance attestation provenance

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

v0.25.78

1 finding

LOW No provenance attestation provenance

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

v0.25.77

1 finding

LOW No provenance attestation provenance

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

v0.25.76

1 finding

LOW No provenance attestation provenance

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

v0.25.75

1 finding

LOW No provenance attestation provenance

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

v0.25.74

1 finding

LOW No provenance attestation provenance

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

v0.25.73

1 finding

LOW No provenance attestation provenance

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

v0.25.72

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.71

1 finding

LOW No provenance attestation provenance

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

v0.25.70

1 finding

LOW No provenance attestation provenance

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

v0.25.69

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.68

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.67

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.66

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.65

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.64

1 finding

LOW No provenance attestation provenance

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

v0.25.63

1 finding

LOW No provenance attestation provenance

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

v0.25.62

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.61

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.60

1 finding

LOW No provenance attestation provenance

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

v0.25.59

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.58

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.57

1 finding

LOW No provenance attestation provenance

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

v0.25.56

1 finding

LOW No provenance attestation provenance

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

v0.25.55

1 finding

LOW No provenance attestation provenance

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

v0.25.54

1 finding

LOW No provenance attestation provenance

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

v0.25.53

1 finding

LOW No provenance attestation provenance

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

v0.25.52

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.51

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.50

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.49

1 finding

LOW No provenance attestation provenance

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

v0.25.48

1 finding

LOW No provenance attestation provenance

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

v0.25.47

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.46

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.45

1 finding

LOW No provenance attestation provenance

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

v0.25.44

1 finding

LOW No provenance attestation provenance

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

v0.25.43

1 finding

LOW No provenance attestation provenance

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

v0.25.42

1 finding

LOW No provenance attestation provenance

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

v0.25.41

1 finding

LOW No provenance attestation provenance

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

v0.25.40

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.39

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.38

1 finding

LOW No provenance attestation provenance

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

v0.25.37

1 finding

LOW No provenance attestation provenance

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

v0.25.36

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@hestia-earth/api' is 1 edit(s) away from popular package 'hapi'.

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.

v0.25.35

1 finding

LOW No provenance attestation provenance

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

v0.25.34

1 finding

LOW No provenance attestation provenance

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

v0.25.33

1 finding

LOW No provenance attestation provenance

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

v0.25.32

1 finding

LOW No provenance attestation provenance

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