@bifravst/aws-cdk-lambda-helpers
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.0.95 | 5 / 19 | |
| 4.0.94 | 5 / 19 | |
| 3.5.139 | 6 / 18 | |
| 3.5.138 | 6 / 18 | |
| 3.5.137 | 6 / 18 | |
| 3.5.136 | 6 / 18 | |
| 3.5.135 | 6 / 18 | |
| 3.5.134 | 6 / 18 | |
| 3.5.133 | 6 / 18 | |
| 3.5.132 | 6 / 18 | |
| 3.5.131 | 6 / 18 | |
| 3.5.130 | 6 / 18 | |
| 3.5.129 | 6 / 18 | |
| 3.5.128 | 6 / 18 | |
| 3.5.127 | 6 / 18 | |
| 3.5.126 | 6 / 18 | |
| 3.5.125 | 6 / 18 | |
| 3.5.124 | 6 / 18 | |
| 3.5.123 | 6 / 18 | |
| 3.5.122 | 6 / 18 | |
| 3.5.121 | 6 / 18 |
v4.0.95
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.94
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.