@agentc7/ac7
Meta-package for ac7 — installs the complete agent control plane (cli, server, sdk, core) in one command.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @agentc7/ac7 is a meta-package for the ac7 project; Levenshtein match to ajv is coincidental. | ai | |
| phantom-deps | phantom-dep:@agentc7/sdk | AI (phantom-deps): Meta-package declares org-sibling deps without importing them directly; expected pattern. | ai | |
| phantom-deps | phantom-dep:@agentc7/core | AI (phantom-deps): Meta-package declares org-sibling deps without importing them directly; expected pattern. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 4 / 0 | |
| 0.0.8 | 4 / 0 | |
| 0.0.7 | 4 / 0 | |
| 0.0.6 | 4 / 0 | |
| 0.0.5 | 4 / 0 | |
| 0.0.4 | 4 / 0 | |
| 0.0.3 | 4 / 0 | |
| 0.0.2 | 4 / 0 | |
| 0.0.1 | 4 / 0 |
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.