@awebai/aw
CLI for the aWeb agent coordination protocol
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Canonical prebuilt-binary selection pattern via platform-specific optional deps; stable for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @awebai/aw with matching GitHub org; Levenshtein match to 'pg' is spurious. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @awebai/aw with matching GitHub org; Levenshtein match to 'qs' is spurious. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @awebai/aw with matching GitHub org; Levenshtein match to 'ajv' is spurious. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in install.js to execute platform binary; consistent with prebuilt-binary install pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves package.json for version lookup only; not loading arbitrary user input. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.24.3 | 0 / 0 | |
| 1.24.2 | 0 / 0 | |
| 1.24.1 | 0 / 0 | |
| 1.24.0 | 0 / 0 | |
| 1.23.0 | 0 / 0 | |
| 1.22.0 | 0 / 0 | |
| 1.21.3 | 0 / 0 | |
| 1.21.0 | 0 / 0 | |
| 1.20.8 | 0 / 0 | |
| 1.20.7 | 0 / 0 | |
| 1.20.6 | 0 / 0 | |
| 1.20.5 | 0 / 0 | |
| 1.20.4 | 0 / 0 | |
| 1.20.2 | 0 / 0 | |
| 1.20.1 | 0 / 0 | |
| 1.19.1 | 0 / 0 | |
| 1.19.0 | 0 / 0 | |
| 1.18.7 | 0 / 0 | |
| 1.18.6 | 0 / 0 | |
| 1.1.7 | 0 / 0 | |
| 0.12.0 | 0 / 0 | |
| 0.11.0 | 0 / 0 |
v1.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.