@liflig/cdk-lambda-config
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish with no code changes; consistent with low-activity maintenance package. | ai |
Versions (showing 87 of 87)
| Version | Deps | Published |
|---|---|---|
| 1.7.36 | 0 / 23 | |
| 1.7.35 | 0 / 23 | |
| 1.7.34 | 0 / 23 | |
| 1.7.33 | 0 / 23 | |
| 1.7.32 | 0 / 23 | |
| 1.7.31 | 0 / 23 | |
| 1.7.30 | 0 / 23 | |
| 1.7.29 | 0 / 23 | |
| 1.7.28 | 0 / 23 | |
| 1.7.27 | 0 / 23 | |
| 1.7.26 | 0 / 23 | |
| 1.7.25 | 0 / 23 | |
| 1.7.24 | 0 / 23 | |
| 1.7.23 | 0 / 23 | |
| 1.7.22 | 0 / 23 | |
| 1.7.21 | 0 / 23 | |
| 1.7.20 | 0 / 23 | |
| 1.7.19 | 0 / 23 | |
| 1.7.18 | 0 / 23 | |
| 1.7.17 | 0 / 23 | |
| 1.7.16 | 0 / 23 | |
| 1.7.15 | 0 / 23 | |
| 1.7.14 | 0 / 23 | |
| 1.7.13 | 0 / 23 | |
| 1.7.12 | 0 / 23 | |
| 1.7.11 | 0 / 23 | |
| 1.7.10 | 0 / 23 | |
| 1.7.9 | 0 / 23 | |
| 1.7.8 | 0 / 23 | |
| 1.7.7 | 0 / 23 | |
| 1.7.6 | 0 / 23 | |
| 1.7.5 | 0 / 23 | |
| 1.7.4 | 0 / 23 | |
| 1.7.3 | 0 / 23 | |
| 1.7.2 | 0 / 23 | |
| 1.7.1 | 0 / 23 | |
| 1.7.0 | 0 / 23 | |
| 1.6.0 | 0 / 23 | |
| 1.5.23 | 0 / 30 | |
| 1.5.22 | 0 / 30 | |
| 1.5.21 | 0 / 30 | |
| 1.5.20 | 0 / 30 | |
| 1.5.19 | 0 / 30 | |
| 1.5.18 | 0 / 30 | |
| 1.5.17 | 0 / 30 | |
| 1.5.16 | 0 / 30 | |
| 1.5.15 | 0 / 30 | |
| 1.5.14 | 0 / 30 | |
| 1.5.13 | 0 / 30 | |
| 1.5.12 | 0 / 30 | |
| 1.5.11 | 0 / 30 | |
| 1.5.10 | 0 / 30 | |
| 1.5.9 | 0 / 30 | |
| 1.5.8 | 0 / 30 | |
| 1.5.7 | 0 / 30 | |
| 1.5.6 | 0 / 31 | |
| 1.5.4 | 0 / 31 | |
| 1.5.3 | 0 / 31 | |
| 1.5.2 | 0 / 29 | |
| 1.5.1 | 0 / 29 | |
| 1.5.0 | 0 / 29 | |
| 1.4.19 | 0 / 29 | |
| 1.4.18 | 0 / 29 | |
| 1.4.17 | 0 / 29 | |
| 1.4.16 | 0 / 29 | |
| 1.4.15 | 0 / 29 | |
| 1.4.14 | 0 / 29 | |
| 1.4.13 | 0 / 29 | |
| 1.4.12 | 0 / 29 | |
| 1.4.11 | 0 / 29 | |
| 1.4.10 | 0 / 29 | |
| 1.4.9 | 0 / 29 | |
| 1.4.8 | 0 / 29 | |
| 1.4.7 | 0 / 29 | |
| 1.4.6 | 0 / 29 | |
| 1.4.5 | 0 / 29 | |
| 1.4.4 | 0 / 29 | |
| 1.4.3 | 0 / 29 | |
| 1.4.2 | 0 / 29 | |
| 1.4.1 | 0 / 29 | |
| 1.4.0 | 0 / 29 | |
| 1.3.1 | 0 / 29 | |
| 1.3.0 | 0 / 29 | |
| 1.2.0 | 0 / 29 | |
| 1.1.1 | 0 / 29 | |
| 1.1.0 | 0 / 29 | |
| 1.0.0 | 0 / 29 |
v1.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.