@liflig/cdk-lambda-config No license 44 versions

@liflig/cdk-lambda-config

npm Repository Homepage

44

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

capra-cijol-capraconsultinghalvorlinder-cevan-boonesondrehavsba.capraconsulting

Keywords

cdklambdaconfig

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from capra-ci to GitHub Actions is consistent with org's CI migration; SLSA provenance attestation confirms legitimate CI publish.	ai	2026/05/09
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by CI-attested publish with no code changes; consistent with low-activity maintenance package.	ai	2026/05/09

Versions (showing 44 of 44)

Version	Deps	Published
1.7.36	0 / 23	2026-03-07
1.7.35	0 / 23	2026-03-03
1.7.34	0 / 23	2026-03-02
1.7.33	0 / 23	2026-02-15
1.7.32	0 / 23	2026-02-14
1.7.31	0 / 23	2026-02-12
1.7.30	0 / 23	2026-02-07
1.7.29	0 / 23	2026-02-05
1.7.28	0 / 23	2026-01-31
1.7.27	0 / 23	2026-01-29
1.7.26	0 / 23	2026-01-14
1.7.25	0 / 23	2025-12-21
1.7.24	0 / 23	2025-12-20
1.7.23	0 / 23	2025-11-22
1.7.22	0 / 23	2025-11-08
1.7.21	0 / 23	2025-11-01
1.7.20	0 / 23	2025-10-31
1.7.19	0 / 23	2025-10-21
1.7.18	0 / 23	2025-10-14
1.7.17	0 / 23	2025-10-11
1.7.16	0 / 23	2025-10-04
1.7.15	0 / 23	2025-10-03
1.7.14	0 / 23	2025-09-18
1.7.13	0 / 23	2025-09-16
1.7.12	0 / 23	2025-09-15
1.7.11	0 / 23	2025-08-27
1.7.10	0 / 23	2025-08-22
1.7.9	0 / 23	2025-08-17
1.7.8	0 / 23	2025-08-16
1.7.7	0 / 23	2025-08-03
1.7.6	0 / 23	2025-08-01
1.7.5	0 / 23	2025-07-28
1.7.4	0 / 23	2025-07-28
1.7.3	0 / 23	2025-07-19
1.7.2	0 / 23	2025-07-15
1.7.1	0 / 23	2025-07-12
1.7.0	0 / 23	2025-07-01
1.6.0	0 / 23	2025-07-01
1.5.23	0 / 30	2025-06-18
1.5.22	0 / 30	2025-05-24
1.5.21	0 / 30	2025-05-10
1.5.20	0 / 30	2025-05-05
1.5.19	0 / 30	2025-04-29
1.5.18	0 / 30	2025-04-28

v1.7.36

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.35

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

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.19

2 findings

HIGH Publisher changed: capra-ci → GitHub Actions (on 2025-10-21) provenance

This version was published by a different npm account than previous versions on 2025-10-21. This could indicate a legitimate maintainer transition or an account compromise.

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.18

1 finding

LOW No provenance attestation provenance

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

v1.7.17

1 finding

LOW No provenance attestation provenance

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

v1.7.16

1 finding

LOW No provenance attestation provenance

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

v1.7.15

1 finding

LOW No provenance attestation provenance

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

v1.7.14

1 finding

LOW No provenance attestation provenance

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

v1.7.13

1 finding

LOW No provenance attestation provenance

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

v1.7.12

1 finding

LOW No provenance attestation provenance

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

v1.7.11

1 finding

LOW No provenance attestation provenance

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

v1.7.10

1 finding

LOW No provenance attestation provenance

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

v1.7.9

1 finding

LOW No provenance attestation provenance

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

v1.7.8

1 finding

LOW No provenance attestation provenance

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

v1.7.7

1 finding

LOW No provenance attestation provenance

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

v1.7.6

1 finding

LOW No provenance attestation provenance

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

v1.7.5

1 finding

LOW No provenance attestation provenance

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

v1.7.4

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

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.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.5.23

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.5.22

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.5.21

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.5.20

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.5.19

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.5.18

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.