@axlsdk/axl
TypeScript SDK for orchestrating Agentic Systems
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 | no-provenance | AI (provenance): Package has no CI provenance setup; consistent across versions, not a malware signal. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped SDK package with distinct purpose; Levenshtein match to ajv is coincidental, not impersonation. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.18.2 | 0 / 11 | |
| 0.18.1 | 0 / 11 | |
| 0.18.0 | 0 / 11 | |
| 0.17.9 | 0 / 11 | |
| 0.17.8 | 0 / 11 | |
| 0.17.7 | 0 / 11 | |
| 0.17.6 | 0 / 11 | |
| 0.17.5 | 0 / 11 | |
| 0.17.4 | 0 / 11 | |
| 0.17.3 | 0 / 11 | |
| 0.17.2 | 0 / 11 | |
| 0.17.1 | 0 / 11 | |
| 0.17.0 | 0 / 11 | |
| 0.16.1 | 0 / 11 | |
| 0.16.0 | 0 / 11 | |
| 0.15.0 | 0 / 11 | |
| 0.14.0 | 0 / 11 | |
| 0.13.8 | 0 / 11 | |
| 0.13.7 | 0 / 11 | |
| 0.13.6 | 0 / 11 | |
| 0.13.5 | 0 / 10 | |
| 0.13.4 | 0 / 10 | |
| 0.13.3 | 0 / 10 | |
| 0.13.2 | 0 / 10 | |
| 0.13.1 | 0 / 10 | |
| 0.13.0 | 0 / 10 | |
| 0.12.0 | 0 / 10 | |
| 0.11.6 | 0 / 10 | |
| 0.11.5 | 0 / 10 | |
| 0.11.4 | 0 / 10 | |
| 0.11.3 | 0 / 10 | |
| 0.11.2 | 0 / 10 | |
| 0.11.1 | 0 / 10 | |
| 0.11.0 | 0 / 10 | |
| 0.10.3 | 0 / 10 | |
| 0.10.0 | 0 / 10 | |
| 0.6.0 | 1 / 9 | |
| 0.3.0 | 1 / 9 | |
| 0.2.0 | 1 / 9 | |
| 0.1.1 | 1 / 9 | |
| 0.1.0 | 1 / 9 |
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boulder_midweek.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boulder_midweek.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boulder_midweek.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boulder_midweek.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.