@cloud-copilot/iam-simulate
Simulate evaluation of AWS IAM policies
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 13 of 115)
| Version | Deps | Published |
|---|---|---|
| 0.1.45 | 3 / 12 | |
| 0.1.44 | 3 / 12 | |
| 0.1.43 | 3 / 12 | |
| 0.1.42 | 3 / 12 | |
| 0.1.41 | 3 / 12 | |
| 0.1.40 | 3 / 12 | |
| 0.1.39 | 3 / 12 | |
| 0.1.38 | 3 / 12 | |
| 0.1.37 | 2 / 12 | |
| 0.1.36 | 2 / 12 | |
| 0.1.35 | 2 / 12 | |
| 0.1.34 | 2 / 12 | |
| 0.1.33 | 2 / 12 |
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.