@0xsequence/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 @0xsequence package; Levenshtein match to 'hapi' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @0xsequence package; no relation to 'pg'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @0xsequence package; no relation to 'joi'. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @0xsequence package; no relation to 'ajv'. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.0.11 | 0 / 4 | |
| 3.0.10 | 0 / 4 | |
| 3.0.9 | 0 / 4 | |
| 3.0.8 | 0 / 4 | |
| 3.0.7 | 0 / 4 | |
| 3.0.6 | 0 / 4 | |
| 3.0.5 | 0 / 4 | |
| 3.0.4 | 0 / 4 | |
| 3.0.3 | 0 / 4 | |
| 3.0.2 | 0 / 4 | |
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.3.44 | 0 / 0 | |
| 2.3.43 | 0 / 0 | |
| 2.3.42 | 0 / 0 | |
| 2.3.41 | 0 / 0 | |
| 2.3.40 | 0 / 0 | |
| 2.3.39 | 0 / 0 | |
| 2.3.38 | 0 / 0 | |
| 2.3.37 | 0 / 0 | |
| 2.3.36 | 0 / 0 | |
| 2.3.35 | 0 / 0 | |
| 2.3.34 | 0 / 0 |
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.