← Home

@aligent/cdk-header-change-detection

npm Repository Homepage

![TypeScript version](https://img.shields.io/github/package-json/dependency-version/aligent/cdk-constructs/dev/typescript?filename=packages/constructs/header-change-detection/package.json&color=red) ![AWS CDK version](https://img.shields.io/github/package

15
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jarrod.swiftaligent-danielvanderploegaligent-bottom.thorogood

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:lib/header-change-detection.js AI (source-diff): Standard tsc-compiled CDK construct output; long lines are from bundled JS, not obfuscation. Stable pattern for this package. ai
phantom-deps phantom-dep:axios AI (phantom-deps): Config-file reference; stable pattern for this package type. ai
phantom-deps phantom-dep:source-map-support AI (phantom-deps): Config-file reference; stable pattern for this package type. ai
phantom-deps phantom-dep:@aws-sdk/client-sns AI (phantom-deps): Framework-scoped AWS SDK; loaded by CDK convention, not direct import. ai
phantom-deps phantom-dep:@aws-sdk/client-dynamodb AI (phantom-deps): Framework-scoped AWS SDK; loaded by CDK convention, not direct import. ai

Versions (showing 15 of 15)

Version Deps Published
1.7.10 4 / 7
1.7.9 4 / 7
1.7.8 4 / 7
1.7.7 4 / 7
1.7.6 4 / 7
1.7.5 4 / 7
1.7.4 4 / 7
1.7.2 4 / 7
1.7.1 4 / 7
1.7.0 4 / 7
1.6.1 4 / 7
1.6.0 4 / 7
1.5.0 4 / 7
1.4.0 4 / 7
1.3.0 4 / 7

v1.7.10

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.2

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.

v1.7.1

2 findings
HIGH New obfuscated file: lib/header-change-detection.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.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.

v1.3.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.