Summary
Right after "Build from source", the guide runs
cp bin/complyctl-provider-openscap ~/.complytime/providers/. That binary is not produced
by the documented make build — it is built from a separate repository
(complytime/complytime-providers) that the page never mentions. A user following the page
literally cannot install a provider, which blocks scanning entirely.
Affected
- Page:
content/docs/getting-started/_index.md (lines 76–78)
Documented steps
# _index.md:76-78
mkdir -p ~/.complytime/providers
cp bin/complyctl-provider-openscap ~/.complytime/providers/
Steps to reproduce
- Clone
complytime/complyctl and run make build as the page instructs.
- Run
cp bin/complyctl-provider-openscap ~/.complytime/providers/.
Expected
The provider binary exists in bin/ after the documented build, and the copy succeeds.
Actual
$ cp bin/complyctl-provider-openscap ~/.complytime/providers/
cp: cannot stat 'bin/complyctl-provider-openscap': No such file or directory (exit 1)
make build compiles ./cmd/... only (complyctl/Makefile:71), and bin/ afterwards
contains:
behavioral-report complyctl mock-oci-registry test-provider
There is no complyctl-provider-openscap. That binary is built in
complytime/complytime-providers via
go build … -o bin/complyctl-provider-openscap ./cmd/openscap-provider
(complytime-providers/Makefile). The page jumps from "build complyctl" to "copy the
openscap provider" with no clone, no build, and no link to the providers repo.
The project's own in-repo complyctl/docs/QUICK_START.md gets this right — it has a
provider table linking to the complytime-providers repo.
Suggested fix
Add the missing provider build before the cp: clone and make complytime-providers,
then cp from its bin/. Alternatively, ship the openscap provider as a documented
release asset and copy from there. Either way, stop implying that the complyctl build emits
the provider binary.
Related: #65, complytime/complytime-providers#91
Issue created with the help of Claude Opus 4.6
Summary
Right after "Build from source", the guide runs
cp bin/complyctl-provider-openscap ~/.complytime/providers/. That binary is not producedby the documented
make build— it is built from a separate repository(
complytime/complytime-providers) that the page never mentions. A user following the pageliterally cannot install a provider, which blocks scanning entirely.
Affected
content/docs/getting-started/_index.md(lines 76–78)Documented steps
Steps to reproduce
complytime/complyctland runmake buildas the page instructs.cp bin/complyctl-provider-openscap ~/.complytime/providers/.Expected
The provider binary exists in
bin/after the documented build, and the copy succeeds.Actual
make buildcompiles./cmd/...only (complyctl/Makefile:71), andbin/afterwardscontains:
There is no
complyctl-provider-openscap. That binary is built incomplytime/complytime-providersviago build … -o bin/complyctl-provider-openscap ./cmd/openscap-provider(
complytime-providers/Makefile). The page jumps from "build complyctl" to "copy theopenscap provider" with no clone, no build, and no link to the providers repo.
The project's own in-repo
complyctl/docs/QUICK_START.mdgets this right — it has aprovider table linking to the
complytime-providersrepo.Suggested fix
Add the missing provider build before the
cp: clone andmakecomplytime-providers,then
cpfrom itsbin/. Alternatively, ship the openscap provider as a documentedrelease asset and copy from there. Either way, stop implying that the complyctl build emits
the provider binary.
Related: #65, complytime/complytime-providers#91
Issue created with the help of Claude Opus 4.6