@aos-harness/adapter-shared
Shared base classes and utilities for AOS Harness platform adapters.
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 |
|---|---|---|---|---|
| semgrep | semgrep:silent-process-exec | AI (semgrep): Detached spawn is used to open a file in an allowlist-validated editor; not a malicious pattern. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same allowlist-guarded editor-open pattern; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 2 / 3 | |
| 0.8.5 | 2 / 3 | |
| 0.8.4 | 2 / 3 | |
| 0.8.3 | 2 / 3 | |
| 0.8.2 | 2 / 3 | |
| 0.8.1 | 2 / 3 | |
| 0.8.0 | 2 / 3 | |
| 0.7.1 | 2 / 3 | |
| 0.7.0 | 2 / 3 | |
| 0.5.2 | 2 / 3 | |
| 0.5.1 | 2 / 3 | |
| 0.5.0 | 2 / 3 | |
| 0.4.2 | 2 / 3 | |
| 0.4.1 | 2 / 3 |
v0.9.0
3 findingsSilent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/aos-engineer/aos-harness/blob/e41c706284a40e4bf5d1e4dd88610c3ed72069c8/src/base-workflow.ts#L181 179 | throw new Error(`Editor "${editor}" is not in the allowed list: ${[...BaseWorkflow.ALLOWED_EDITORS].join(", ")}`); 180 | } > 181 | spawn(editor, [safePath], { detached: true, stdio: "ignore" }).unref(); 182 | } 183 |
Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/aos-engineer/aos-harness/blob/e41c706284a40e4bf5d1e4dd88610c3ed72069c8/src/base-workflow.ts#L181 179 | throw new Error(`Editor "${editor}" is not in the allowed list: ${[...BaseWorkflow.ALLOWED_EDITORS].join(", ")}`); 180 | } > 181 | spawn(editor, [safePath], { detached: true, stdio: "ignore" }).unref(); 182 | } 183 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.