@aws-cdk/aws-codeguruprofiler
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
romainmulleramzn-ossrix0rrraws-cdk-team
Keywords
awscdkconstructsAWS::CodeGuruProfileraws-codeguruprofiler
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Expected lockstep release pattern for aws-cdk monorepo packages. | ai | |
| source-diff | obfuscated-file:lib/profiling-group.js | AI (source-diff): Legit compiled CDK construct code, not obfuscation. | ai | |
| source-diff | obfuscated-file:test/profiling-group.test.js | AI (source-diff): Test file with long CFN template literals, not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): New feature (profiling-group) added by official maintainer, not injected payload. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dependency is official sibling @aws-cdk/aws-iam package. | ai |
v1.32.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.