@aws-cdk/aws-efs — Greenflagged

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

awscdkconstructsefs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): All new deps are same-org @aws-cdk/* siblings, standard for this monorepo.	ai	2026/07/21
source-diff	obfuscated-file:lib/efs-canned-metrics.generated.js	AI (source-diff): Auto-generated metrics file, plain code despite long lines.	ai	2026/07/21
source-diff	obfuscated-file:lib/access-point.js	AI (source-diff): Readable compiled TS, not obfuscated; new AccessPoint feature file.	ai	2026/07/21
phantom-deps	phantom-dep:@aws-cdk/cloud-assembly-schema	AI (phantom-deps): Same-org CDK dep, standard cross-package pattern.	ai	2026/07/21
phantom-deps	phantom-dep:constructs	AI (phantom-deps): jsii construct base dep, used indirectly via config.	ai	2026/07/21
source-diff	obfuscated-file:test/access-point.test.js	AI (source-diff): Test file, plain readable code.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): Old package with regular monorepo-wide release cadence; not indicative of takeover.	ai	2026/07/21
npm-metadata	url-dep:cfn2ts	AI (npm-metadata): Monorepo-internal build tool dependency, standard for aws-cdk packages.	ai	2026/07/21
npm-metadata	url-dep:cdk-build-tools	AI (npm-metadata): Monorepo-internal build tool dependency, standard for aws-cdk packages.	ai	2026/07/21
npm-metadata	url-dep:pkglint	AI (npm-metadata): Monorepo-internal build tool dependency, standard for aws-cdk packages.	ai	2026/07/21
phantom-deps	phantom-dep:@aws-cdk/cx-api	AI (phantom-deps): Same-org internal CDK dep, used transitively; known FP pattern for monorepo packages.	ai	2026/07/21
source-diff	obfuscated-file:test/efs-file-system.test.js	AI (source-diff): Same false positive pattern in test file.	ai	2026/07/21
source-diff	obfuscated-file:lib/efs-file-system.js	AI (source-diff): Long-line heuristic false positive on transpiled TS enum/output, not real obfuscation.	ai	2026/07/21

Versions (showing 42 of 242)

Version	Deps	Published
1.32.1	5 / 4	2020-04-09
1.32.0	5 / 4	2020-04-07
1.31.0	5 / 4	2020-03-24
1.30.0	5 / 4	2020-03-18
1.29.0	5 / 4	2020-03-18
1.28.0	4 / 4	2020-03-16
1.27.0	1 / 4	2020-03-03
1.26.0	1 / 4	2020-02-26
1.25.0	1 / 4	2020-02-19
1.24.0	1 / 4	2020-02-14
1.23.0	1 / 4	2020-02-07
1.22.0	1 / 4	2020-01-23
1.21.1	1 / 4	2020-01-16
1.21.0	1 / 4	2020-01-16
1.20.0	1 / 4	2020-01-08
1.19.0	1 / 4	2019-12-17
1.18.0	1 / 4	2019-11-25
1.17.1	1 / 4	2019-11-19
1.17.0	1 / 4	2019-11-19
1.16.3	1 / 4	2019-11-13
1.16.2	1 / 4	2019-11-12
1.16.1	1 / 4	2019-11-12
1.16.0	1 / 4	2019-11-11
1.15.0	1 / 4	2019-10-28
1.14.0	1 / 4	2019-10-22
1.13.1	1 / 4	2019-10-15
1.13.0	1 / 4	2019-10-15
1.12.0	1 / 4	2019-10-07
1.11.0	1 / 4	2019-10-02
1.10.1	1 / 4	2019-10-01
1.10.0	1 / 4	2019-09-30
1.9.0	1 / 4	2019-09-20
1.8.0	1 / 4	2019-09-10
1.7.0	1 / 4	2019-09-06
1.6.1	1 / 4	2019-08-29
1.6.0	1 / 4	2019-08-27
1.5.0	1 / 4	2019-08-21
1.4.0	1 / 4	2019-08-14
1.3.0	1 / 4	2019-08-02
1.2.0	1 / 4	2019-07-25
1.1.0	1 / 4	2019-07-19
1.0.0	1 / 4	2019-07-11

v1.32.1

3 findings

HIGH New obfuscated file: lib/efs-file-system.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.

HIGH New obfuscated file: test/efs-file-system.test.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.32.0

3 findings

HIGH New obfuscated file: lib/efs-file-system.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.

HIGH New obfuscated file: test/efs-file-system.test.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.31.0

3 findings

HIGH New obfuscated file: lib/efs-file-system.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.

HIGH New obfuscated file: test/efs-file-system.test.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.30.0

3 findings

HIGH New obfuscated file: lib/efs-file-system.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.

HIGH New obfuscated file: test/efs-file-system.test.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.29.0

3 findings

HIGH New obfuscated file: lib/efs-file-system.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.

HIGH New obfuscated file: test/efs-file-system.test.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.28.0

3 findings

HIGH New obfuscated file: lib/efs-file-system.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.

HIGH New obfuscated file: test/efs-file-system.test.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.27.0

1 finding

LOW No provenance attestation provenance

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

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.0

1 finding

LOW No provenance attestation provenance

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

v1.24.0

1 finding

LOW No provenance attestation provenance

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

v1.23.0

1 finding

LOW No provenance attestation provenance

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

v1.22.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.21.1

1 finding

LOW No provenance attestation provenance

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

v1.21.0

1 finding

LOW No provenance attestation provenance

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

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.19.0

1 finding

LOW No provenance attestation provenance

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

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.1

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.3

1 finding

LOW No provenance attestation provenance

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

v1.16.2

1 finding

LOW No provenance attestation provenance

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

v1.16.1

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

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