@juit/lib-aws-mock
Easy Mocking for AWS SDK v3
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 (pfumagalli) to GitHub Actions CI/CD with SLSA attestation; legitimate automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy ended with CI/CD adoption; SLSA provenance confirms legitimate automated pipeline. | ai |
Versions (showing 100 of 115)
| Version | Deps | Published |
|---|---|---|
| 1.2.151 | 1 / 2 | |
| 1.2.150 | 1 / 2 | |
| 1.2.149 | 1 / 2 | |
| 1.2.148 | 1 / 2 | |
| 1.2.147 | 1 / 2 | |
| 1.2.146 | 1 / 2 | |
| 1.2.145 | 1 / 2 | |
| 1.2.144 | 1 / 2 | |
| 1.2.143 | 1 / 2 | |
| 1.2.142 | 1 / 2 | |
| 1.2.141 | 1 / 2 | |
| 1.2.140 | 1 / 2 | |
| 1.2.139 | 1 / 2 | |
| 1.2.138 | 1 / 2 | |
| 1.2.137 | 1 / 2 | |
| 1.2.136 | 1 / 2 | |
| 1.2.135 | 1 / 2 | |
| 1.2.134 | 1 / 2 | |
| 1.2.133 | 1 / 2 | |
| 1.2.132 | 1 / 2 | |
| 1.2.131 | 1 / 2 | |
| 1.2.130 | 1 / 2 | |
| 1.2.129 | 1 / 2 | |
| 1.2.128 | 1 / 2 | |
| 1.2.127 | 1 / 2 | |
| 1.2.126 | 1 / 2 | |
| 1.2.125 | 1 / 2 | |
| 1.2.124 | 1 / 2 | |
| 1.2.123 | 1 / 2 | |
| 1.2.122 | 1 / 2 | |
| 1.2.121 | 1 / 2 | |
| 1.2.120 | 1 / 2 | |
| 1.2.119 | 1 / 2 | |
| 1.2.118 | 1 / 2 | |
| 1.2.117 | 1 / 2 | |
| 1.2.116 | 1 / 2 | |
| 1.2.115 | 1 / 2 | |
| 1.2.114 | 1 / 2 | |
| 1.2.113 | 1 / 2 | |
| 1.2.112 | 1 / 2 | |
| 1.2.111 | 1 / 2 | |
| 1.2.110 | 1 / 2 | |
| 1.2.109 | 1 / 2 | |
| 1.2.108 | 1 / 2 | |
| 1.2.107 | 1 / 2 | |
| 1.2.106 | 1 / 2 | |
| 1.2.105 | 1 / 2 | |
| 1.2.104 | 1 / 2 | |
| 1.2.103 | 1 / 2 | |
| 1.2.102 | 1 / 2 | |
| 1.2.101 | 1 / 2 | |
| 1.2.100 | 1 / 2 | |
| 1.2.99 | 1 / 2 | |
| 1.2.98 | 1 / 2 | |
| 1.2.97 | 1 / 2 | |
| 1.2.96 | 1 / 2 | |
| 1.2.95 | 1 / 2 | |
| 1.2.94 | 1 / 2 | |
| 1.2.93 | 1 / 2 | |
| 1.2.92 | 1 / 2 | |
| 1.2.91 | 1 / 2 | |
| 1.2.90 | 1 / 2 | |
| 1.2.89 | 1 / 2 | |
| 1.2.88 | 1 / 2 | |
| 1.2.87 | 1 / 2 | |
| 1.2.86 | 1 / 2 | |
| 1.2.84 | 1 / 2 | |
| 1.2.83 | 1 / 2 | |
| 1.2.82 | 1 / 2 | |
| 1.2.81 | 1 / 2 | |
| 1.2.80 | 1 / 2 | |
| 1.2.79 | 1 / 2 | |
| 1.2.78 | 1 / 2 | |
| 1.2.77 | 1 / 2 | |
| 1.2.76 | 1 / 2 | |
| 1.2.75 | 1 / 2 | |
| 1.2.74 | 1 / 2 | |
| 1.2.73 | 1 / 2 | |
| 1.2.72 | 1 / 2 | |
| 1.2.71 | 1 / 2 | |
| 1.2.70 | 1 / 2 | |
| 1.2.69 | 1 / 2 | |
| 1.2.68 | 1 / 2 | |
| 1.2.67 | 1 / 2 | |
| 1.2.66 | 1 / 2 | |
| 1.2.65 | 1 / 2 | |
| 1.2.64 | 1 / 2 | |
| 1.2.63 | 1 / 2 | |
| 1.2.62 | 1 / 2 | |
| 1.2.61 | 1 / 2 | |
| 1.2.60 | 1 / 2 | |
| 1.2.59 | 1 / 2 | |
| 1.2.58 | 1 / 2 | |
| 1.2.57 | 1 / 2 | |
| 1.2.56 | 1 / 2 | |
| 1.2.55 | 1 / 2 | |
| 1.2.54 | 1 / 2 | |
| 1.2.53 | 1 / 2 | |
| 1.2.52 | 1 / 2 | |
| 1.2.51 | 1 / 2 |
v1.2.151
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.150
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.149
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.148
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.147
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.