@aws-cdk/aws-codestarnotifications
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/notification-rule.js | AI (source-diff): jsii-generated lib file, long lines are compiled output not obfuscation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Normal cadence gap for aws-cdk monorepo release trains. | ai |
Versions (showing 20 of 220)
| Version | Deps | Published |
|---|---|---|
| 1.32.1 | 2 / 4 | |
| 1.32.0 | 2 / 4 | |
| 1.31.0 | 2 / 4 | |
| 1.30.0 | 2 / 4 | |
| 1.29.0 | 2 / 4 | |
| 1.28.0 | 1 / 4 | |
| 1.27.0 | 1 / 4 | |
| 1.26.0 | 1 / 4 | |
| 1.25.0 | 1 / 4 | |
| 1.24.0 | 1 / 4 | |
| 1.23.0 | 1 / 4 | |
| 1.22.0 | 1 / 4 | |
| 1.21.1 | 1 / 4 | |
| 1.21.0 | 1 / 4 | |
| 1.20.0 | 1 / 4 | |
| 1.19.0 | 1 / 4 | |
| 1.18.0 | 1 / 4 | |
| 1.17.1 | 1 / 4 | |
| 1.17.0 | 1 / 4 | |
| 1.16.1 | 1 / 4 |
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.