@cef-ai/cli
`cef` — build, typegen, and inspect agents from the command line. Mirrors the runtime contract: bundles emit `globalThis.__cefAgent`, manifests carry the routing table the runtime reads.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cef-ai/transport | AI (dependencies): First-party scoped sibling dep; benign for this package. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap only; trusted publisher with clean history, no behavioral change. | ai | |
| dependencies | unvetted-dep:@cef-ai/widget-runtime | AI (dependencies): Same-org first-party package, consistent with monorepo dependency pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @noble/* and canonicalize are reputable crypto libs; addition is contextually appropriate for a CLI gaining signing features. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @cef-ai/cli is a scoped package in its own namespace; Levenshtein match to 'joi' is a false positive. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.10.3 | 9 / 3 | |
| 1.10.2 | 9 / 3 | |
| 1.10.1 | 9 / 3 | |
| 1.10.0 | 9 / 3 | |
| 1.9.1 | 9 / 3 | |
| 1.9.0 | 9 / 3 | |
| 1.8.0 | 9 / 3 | |
| 1.7.0 | 9 / 3 | |
| 1.6.0 | 8 / 3 | |
| 1.5.0 | 8 / 3 | |
| 1.4.0 | 8 / 3 | |
| 1.3.1 | 8 / 3 | |
| 1.3.0 | 8 / 3 | |
| 1.2.0 | 8 / 2 | |
| 1.1.0 | 8 / 2 | |
| 1.0.0 | 8 / 2 | |
| 0.5.1 | 8 / 2 | |
| 0.5.0 | 8 / 2 | |
| 0.4.1 | 8 / 2 | |
| 0.4.0 | 8 / 2 | |
| 0.3.0 | 5 / 2 | |
| 0.2.7 | 10 / 9 | |
| 0.2.6 | 10 / 9 | |
| 0.2.5 | 10 / 9 | |
| 0.2.4 | 10 / 9 | |
| 0.2.3 | 10 / 9 | |
| 0.2.2 | 10 / 9 | |
| 0.2.1 | 9 / 9 |
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.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: cere-io.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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: cere-io.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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: cere-io.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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: cere-io.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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: cere-io.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.