@xyo-network/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @xyo-network package; Levenshtein match to 'hapi' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @xyo-network package; Levenshtein match to 'pg' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @xyo-network package; Levenshtein match to 'joi' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @xyo-network package; Levenshtein match to 'ajv' is coincidental. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 6.0.9 | 3 / 23 | |
| 6.0.8 | 3 / 24 | |
| 6.0.7 | 3 / 25 | |
| 6.0.6 | 3 / 25 | |
| 6.0.5 | 3 / 27 | |
| 6.0.4 | 3 / 28 | |
| 6.0.3 | 3 / 28 | |
| 6.0.2 | 3 / 28 | |
| 6.0.1 | 3 / 28 | |
| 6.0.0 | 3 / 28 | |
| 5.6.2 | 3 / 28 | |
| 5.6.1 | 3 / 28 | |
| 5.5.2 | 3 / 30 | |
| 5.5.1 | 3 / 30 | |
| 5.5.0 | 1 / 60 | |
| 5.4.1 | 1 / 29 | |
| 5.4.0 | 1 / 29 | |
| 5.3.30 | 1 / 33 | |
| 5.3.29 | 1 / 33 | |
| 5.3.27 | 4 / 23 | |
| 5.3.26 | 4 / 25 | |
| 5.3.25 | 4 / 25 | |
| 5.3.24 | 4 / 25 | |
| 5.3.22 | 4 / 24 | |
| 5.3.20 | 4 / 15 | |
| 5.3.17 | 4 / 14 | |
| 5.3.16 | 4 / 14 | |
| 5.3.15 | 4 / 14 | |
| 5.3.13 | 4 / 14 | |
| 5.3.12 | 4 / 14 | |
| 5.3.11 | 4 / 14 | |
| 5.3.10 | 4 / 14 | |
| 5.3.8 | 4 / 14 | |
| 5.3.7 | 4 / 14 | |
| 5.3.6 | 4 / 13 | |
| 5.3.5 | 4 / 13 | |
| 5.3.4 | 4 / 13 | |
| 5.3.3 | 6 / 12 | |
| 5.3.2 | 6 / 12 | |
| 5.3.1 | 6 / 12 | |
| 5.3.0 | 6 / 12 | |
| 5.2.27 | 6 / 12 | |
| 5.2.25 | 6 / 12 | |
| 5.2.24 | 7 / 12 | |
| 5.2.22 | 7 / 12 | |
| 5.2.20 | 7 / 12 | |
| 5.2.19 | 7 / 12 | |
| 5.2.18 | 7 / 13 | |
| 5.2.17 | 7 / 13 | |
| 5.2.16 | 7 / 13 | |
| 5.2.14 | 7 / 13 | |
| 5.2.13 | 7 / 13 | |
| 5.2.12 | 7 / 13 | |
| 5.2.11 | 7 / 13 | |
| 5.2.10 | 7 / 13 | |
| 5.2.9 | 7 / 13 | |
| 5.2.8 | 7 / 13 | |
| 5.2.7 | 7 / 13 | |
| 5.2.6 | 7 / 13 | |
| 5.2.5 | 7 / 13 | |
| 5.2.1 | 7 / 13 | |
| 5.2.0 | 6 / 14 | |
| 5.1.24 | 6 / 14 | |
| 5.1.23 | 6 / 14 | |
| 5.1.22 | 6 / 14 | |
| 5.1.21 | 6 / 14 | |
| 5.1.20 | 6 / 14 | |
| 5.1.19 | 6 / 14 | |
| 5.1.18 | 6 / 14 | |
| 5.1.17 | 6 / 14 | |
| 5.1.16 | 6 / 14 | |
| 5.1.15 | 6 / 14 | |
| 5.1.14 | 7 / 13 | |
| 5.1.13 | 7 / 13 | |
| 5.1.10 | 7 / 13 | |
| 5.1.9 | 7 / 13 | |
| 5.1.8 | 7 / 13 | |
| 5.1.7 | 7 / 13 | |
| 5.1.6 | 7 / 13 | |
| 5.1.5 | 7 / 13 | |
| 5.1.4 | 7 / 13 | |
| 5.1.3 | 7 / 13 | |
| 5.1.2 | 7 / 13 | |
| 5.1.1 | 7 / 13 | |
| 5.1.0 | 7 / 13 | |
| 5.0.7 | 7 / 13 | |
| 5.0.6 | 7 / 13 | |
| 5.0.5 | 7 / 13 | |
| 5.0.4 | 7 / 13 | |
| 5.0.3 | 7 / 13 | |
| 5.0.2 | 7 / 13 | |
| 5.0.1 | 7 / 13 | |
| 5.0.0 | 7 / 13 |
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-05, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.2
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.30
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.29
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.27
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.26
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.25
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.24
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.22
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.20
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.17
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.16
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.15
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.13
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.12
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.11
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.10
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.8
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.7
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.6
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.5
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.4
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.27
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.25
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.24
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.22
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.20
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.19
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.18
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.17
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.16
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.14
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.13
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.12
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.11
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.10
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.9
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.8
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.7
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.6
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.24
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.23
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.22
2 findingsPackage name '@xyo-network/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.