@cloud-copilot/iam-expand
Expand AWS IAM Actions with Wildcards
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 manual publish to GitHub Actions CI/CD with SLSA attestation; consistent with legitimate automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-automated publish with SLSA provenance; no malicious indicators. | ai | |
| license | copyleft-license:AGPL-3.0-or-later | AI (license): Intentional license choice for this package; stable across versions. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 0.11.77 | 1 / 12 | |
| 0.11.76 | 1 / 12 | |
| 0.11.75 | 1 / 12 | |
| 0.11.74 | 1 / 12 | |
| 0.11.73 | 1 / 12 | |
| 0.11.72 | 1 / 12 | |
| 0.11.71 | 1 / 12 | |
| 0.11.70 | 1 / 12 | |
| 0.11.69 | 1 / 12 | |
| 0.11.68 | 1 / 12 | |
| 0.11.67 | 1 / 12 | |
| 0.11.66 | 1 / 12 | |
| 0.11.65 | 1 / 12 | |
| 0.11.64 | 1 / 12 | |
| 0.11.63 | 1 / 12 | |
| 0.11.62 | 1 / 12 | |
| 0.11.61 | 1 / 12 | |
| 0.11.60 | 1 / 12 | |
| 0.11.59 | 1 / 12 | |
| 0.11.58 | 1 / 12 | |
| 0.11.57 | 1 / 12 | |
| 0.11.56 | 1 / 12 | |
| 0.11.55 | 1 / 12 | |
| 0.11.54 | 1 / 12 | |
| 0.11.53 | 1 / 12 | |
| 0.11.52 | 1 / 12 | |
| 0.11.51 | 1 / 12 | |
| 0.11.50 | 1 / 12 | |
| 0.11.49 | 1 / 12 | |
| 0.11.48 | 1 / 12 | |
| 0.11.47 | 1 / 12 | |
| 0.11.46 | 1 / 12 | |
| 0.11.45 | 1 / 12 | |
| 0.11.44 | 1 / 12 | |
| 0.11.43 | 1 / 12 | |
| 0.11.42 | 1 / 12 | |
| 0.11.41 | 1 / 12 | |
| 0.11.40 | 1 / 12 | |
| 0.11.39 | 1 / 12 | |
| 0.11.38 | 1 / 12 | |
| 0.11.37 | 1 / 12 | |
| 0.11.36 | 1 / 12 | |
| 0.11.35 | 1 / 12 | |
| 0.11.34 | 1 / 12 | |
| 0.11.33 | 1 / 12 | |
| 0.11.32 | 1 / 12 | |
| 0.11.31 | 1 / 12 | |
| 0.11.30 | 1 / 12 | |
| 0.11.29 | 1 / 12 | |
| 0.11.28 | 1 / 12 | |
| 0.11.27 | 1 / 12 | |
| 0.11.26 | 1 / 12 | |
| 0.11.25 | 1 / 12 | |
| 0.11.24 | 1 / 12 | |
| 0.11.23 | 1 / 12 | |
| 0.11.22 | 1 / 12 | |
| 0.11.21 | 1 / 12 | |
| 0.11.20 | 1 / 12 | |
| 0.11.19 | 1 / 12 | |
| 0.11.18 | 1 / 12 | |
| 0.11.17 | 1 / 12 | |
| 0.11.16 | 1 / 12 | |
| 0.11.15 | 1 / 12 | |
| 0.11.14 | 1 / 12 | |
| 0.11.13 | 1 / 12 | |
| 0.11.12 | 1 / 12 | |
| 0.11.11 | 1 / 12 | |
| 0.11.10 | 1 / 12 | |
| 0.11.9 | 1 / 12 | |
| 0.11.8 | 1 / 12 | |
| 0.11.7 | 1 / 12 | |
| 0.11.6 | 1 / 12 | |
| 0.11.5 | 1 / 12 | |
| 0.11.4 | 1 / 12 | |
| 0.11.3 | 1 / 12 | |
| 0.11.2 | 1 / 12 | |
| 0.11.1 | 1 / 12 | |
| 0.11.0 | 0 / 4 | |
| 0.10.0 | 0 / 4 | |
| 0.9.0 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.0 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.0 | 0 / 4 | |
| 0.4.0 | 0 / 4 | |
| 0.3.0 | 0 / 4 | |
| 0.2.0 | 0 / 4 | |
| 0.1.12 | 0 / 4 | |
| 0.1.11 | 0 / 4 | |
| 0.1.10 | 0 / 4 | |
| 0.1.9 | 0 / 4 | |
| 0.1.8 | 0 / 4 | |
| 0.1.7 | 0 / 4 | |
| 0.1.6 | 0 / 4 | |
| 0.1.5 | 0 / 4 | |
| 0.1.4 | 0 / 3 | |
| 0.1.3 | 0 / 3 | |
| 0.1.2 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 |
v0.11.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.