@xylabs/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher with 492 approvals; missing gitHead in one version is low risk given no code changes. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'hapi' is a false positive for this established org. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'pg' is a false positive for this established org. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'joi' is a false positive for this established org. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @xylabs package; Levenshtein match to 'ajv' is a false positive for this established org. | ai |
Versions (showing 14 of 119)
| Version | Deps | Published |
|---|---|---|
| 5.0.13 | 3 / 4 | |
| 5.0.12 | 3 / 4 | |
| 5.0.11 | 3 / 4 | |
| 5.0.10 | 3 / 4 | |
| 5.0.9 | 3 / 4 | |
| 5.0.8 | 3 / 4 | |
| 5.0.7 | 3 / 4 | |
| 5.0.6 | 3 / 4 | |
| 5.0.5 | 3 / 4 | |
| 5.0.4 | 3 / 4 | |
| 5.0.3 | 3 / 4 | |
| 5.0.2 | 3 / 4 | |
| 5.0.1 | 3 / 4 | |
| 5.0.0 | 3 / 4 |
v5.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
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.