@agforge/engine
DefaultAgent with built-in interceptors, MCP client, tool factory, context compression, and error hierarchy for AgForge SDK
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:new-function-constructor | AI (semgrep): Used in json-schema-to-zod conversion with a generated Zod schema string; not user-controlled arbitrary code execution. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions from a public monorepo; absence of Sigstore attestation is common and not a risk signal here. | ai |
v0.1.2
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.