@cloudcomponents/cdk-codepipeline-anchore-inline-scan-action
CodePipeline action to integrate Anchore Engine into your pipeline
Install
TypeScript/JavaScript:
npm i @cloudcomponents/cdk-codepipeline-anchore-inline-scan-action
Python:
pip install cloudcomponents.cdk-codepipeline-anchore-inline-scan-action
How to use
import { CodePipelineAnchoreInlineScanAction } from '@cloudcomponents/cdk-codepipeline-anchore-inline-scan-action';
import { CodePipelineDockerfileLinterAction } from '@cloudcomponents/cdk-codepipeline-dockerfile-linter-action';
import { Stack, StackProps } from 'aws-cdk-lib';
import { Repository } from 'aws-cdk-lib/aws-codecommit';
import { Pipeline, Artifact } from 'aws-cdk-lib/aws-codepipeline';
import { CodeCommitSourceAction } from 'aws-cdk-lib/aws-codepipeline-actions';
import { Construct } from 'constructs';
export class ContainerAuditStack extends Stack {
constructor(scope: Construct, id: string, props?: StackProps) {
super(scope, id, props);
const repository = new Repository(this, 'Repository', {
repositoryName: 'container-audit-repository',
});
const sourceArtifact = new Artifact();
const sourceAction = new CodeCommitSourceAction({
actionName: 'CodeCommit',
repository,
output: sourceArtifact,
branch: 'master',
});
const linterAction = new CodePipelineDockerfileLinterAction({
actionName: 'Linter',
input: sourceArtifact,
});
const vulnScanAction = new CodePipelineAnchoreInlineScanAction({
actionName: 'VulnScan',
input: sourceArtifact,
});
new Pipeline(this, 'Pipeline', {
pipelineName: 'container-audit-pipeline',
stages: [
{
stageName: 'Source',
actions: [sourceAction],
},
{
stageName: 'Audit',
actions: [linterAction, vulnScanAction],
},
],
});
}
}
API Reference
See API.md.
Example
See more complete examples.
License
Metadata
Release files for cloudcomponents.cdk-codepipeline-anchore-inline-scan-action 2.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cloudcomponents.cdk-codepipeline-anchore-inline-scan-action-2.3.0.tar.gz | 137.6 kB | Without provenance | Details for cloudcomponents.cdk-codepipeline-anchore-inline-scan-action-2.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cloudcomponents.cdk_codepipeline_anchore_inline_scan_action-2.3.0-py3-none-any.whl | Python 3 | none | any | Details for cloudcomponents.cdk_codepipeline_anchore_inline_scan_action-2.3.0-py3-none-any.whl |
Total release size: 274.7 kB
Release files / cloudcomponents.cdk-codepipeline-anchore-inline-scan-action-2.3.0.tar.gz
| Download URL | cloudcomponents.cdk-codepipeline-anchore-inline-scan-action-2.3.0.tar.gz |
|---|---|
| Size | 137.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ec81f42f7655ebf17e681f6ee5400b6d4be9e4f099faa0bf143257f1e735e6f
|
|
BLAKE2b-256 checksum How to use checksums |
77f1c4eeac3d5b679ea32b7ded4b9bcd2d92f4c63534e454a797166f52834534
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / cloudcomponents.cdk_codepipeline_anchore_inline_scan_action-2.3.0-py3-none-any.whl
| Download URL | cloudcomponents.cdk_codepipeline_anchore_inline_scan_action-2.3.0-py3-none-any.whl |
|---|---|
| Size | 137.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dea6c51e76978772f13580f1da94c711b8e4fe2bfb617eff04ab34984d112034
|
|
BLAKE2b-256 checksum How to use checksums |
316b7ce6fbe1d476af0234cedb40bee44208107da172a03fd7c829c0d2bccfb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for cloudcomponents.cdk-codepipeline-anchore-inline-scan-action 2.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.