Build an API inventory
Find provider, resource, operation, and source-location evidence across supported languages. Export a machine-readable report for your own tools.
Open source · Built for GitHub Actions
CCE Action reads your source code and turns cloud SDK calls into clear, reviewable evidence. Add one workflow to inventory APIs, review changes, and prepare IAM access requests.
PutObjectbucketUploadUseful on the first run
Cloud usage is often spread across code, tickets, and IAM policies. CCE gives developers and reviewers a common starting point.
Find provider, resource, operation, and source-location evidence across supported languages. Export a machine-readable report for your own tools.
See added and removed Cloud API calls in one pull-request comment. Keep the JSON, Markdown, and SARIF evidence for later.
Give IAM reviewers a concise list of operations found in code. They decide the final policy and resource boundaries.
Quick start
Create .github/workflows/cce.yml in your repository. The workflow checks out your code, runs CCE, and uploads the results.
cce-results artifact.name: CCE
on: [push, pull_request]
permissions:
contents: read
packages: read
jobs:
scan:
uses: stackgenhq/cce-action/.github/workflows/scan.yml@v1
with:
language: AUTO
filter: cloud
@v0.3.0 instead of @v1. The major tag receives compatible updates; an exact release stays fixed.
A real repository, a real result
Scan aws-samples/aws-lambda-extensions at a pinned commit. CCE 0.0.38 examined 313 Python files and emitted 10 AWS evidence rows, including this Secrets Manager call.
Try it without setting up AWS
The example checks out the public repository, runs the Python scan, and uploads cce-public-repo-results. No AWS credentials, deployed application, or CCE account is needed.
{
"files_scanned": 313,
"summary": {
"total_entitlements": 10,
"by_provider": { "AWS": 10 }
},
"example": {
"provider": "AWS",
"resource": "secretsmanager",
"operation": "get_secret_value",
"file": "python-example-telemetry-opensearch-extension/python-example-telemetry-opensearch-extension/telemetry_dispatcher.py",
"line": 19,
"column": 19,
"method": "boto3.client('secretsmanager').get_secret_value"
}
}
The row identifies AWS, Secrets Manager, and get_secret_value. The ten summary rows are evidence records, not ten unique permissions.
File, line, column, method, and signature connect the classification to the code. The full guide links directly to the pinned source line.
An IAM reviewer can evaluate secretsmanager:GetSecretValue, then choose the secret ARN and validate the role. CCE does not grant access automatically.
The scan does not execute code, read secrets, prove runtime coverage, or test effective IAM. Use it alongside human review and runtime validation.
Choose your starting point
Start with a scan, then add only the capabilities your team needs.
Create a Cloud API report, IAM-related exports, and a cloud-neutral E-SBOM.
Post a sticky Cloud API diff, publish SARIF, and optionally fail when new operations appear.
Package code-evidenced operations as versioned JSON for review in your IAM process.
Share an HTML report, API inventory, SARIF, lens lockfile, and suggested CI workflow.
Test a proposed lens against committed fixtures and catch regressions before merging.
- uses: stackgenhq/cce-action@v1
with:
language: AUTO
lens: .cce/internal-sdk.yaml
filter: all
Make CCE speak your language
A lens is a small YAML file that describes the libraries or patterns you want to find. Use one to inventory internal SDKs, legacy clients, or technology-debt patterns alongside built-in cloud mappings.
Designed for responsible review
CCE supports engineering decisions; it does not replace testing, provider documentation, or an IAM reviewer.
No CCE account is needed. Field diagnostics are off unless you explicitly enable them. Basic scans use read-only repository permissions.
Reports connect operations to source locations. Lens hashes and versioned artifacts help reviewers understand what produced a result.
Strict GCP and Azure exports do not publish unverified permission mappings. A missing role export is not silently replaced with a guess.
Dynamic, reflected, or unrecognized wrapped calls may be missed. An empty result does not prove that a service needs no permissions.
CCE identifies operations in source code. Your reviewers remain responsible for resource scope, runtime behavior, organizational policy, and final approval.
Good to know
ubuntu-latest is the simplest choice.AUTO for detection.filter: all when a lens reports categories outside the cloud filter.scan-timeout to keep CI bounded.No. The reusable workflows and composite actions provide a tested CCE version for the run.
Yes. Check out your repository, then use stackgenhq/cce-action@v1 or a focused subaction such as access-request@v1.
They are written to the configured output directory and, in the reusable workflows, uploaded as GitHub Actions artifacts.
No. It is source-code evidence for review. Validate policies against runtime needs and your organization’s requirements.
Start with one repository