@sentio/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 package @sentio/api; Levenshtein match to 'hapi' is coincidental, not a squatting attempt. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @sentio/api; no relation to 'pg'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @sentio/api; no relation to 'joi'. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @sentio/api; no relation to 'ajv'. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): app.sentio.xyz is the legitimate Sentio platform baseUrl; stable for this generated API client package. | ai |
v1.0.4
2 findingsPackage name '@sentio/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.
v1.0.3
2 findingsPackage name '@sentio/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.
v1.0.2
2 findingsPackage name '@sentio/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.