@axiomhq/js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @axiomhq/js is the official Axiom SDK, not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @axiomhq/js is the official Axiom SDK, not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @axiomhq/js is the official Axiom SDK, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped package @axiomhq/js is the official Axiom SDK, not a typosquat of rxjs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @axiomhq/js is the official Axiom SDK, not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @axiomhq/js is the official Axiom SDK, not a typosquat of ajv. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 1 / 2 | |
| 1.7.0 | 1 / 2 | |
| 1.6.1 | 1 / 2 | |
| 1.6.0 | 1 / 2 | |
| 1.5.0 | 1 / 2 | |
| 1.4.0 | 1 / 2 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.0 | 2 / 0 | |
| 1.1.1 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.0 | 2 / 0 |
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.