@gapi/core

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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Established scoped GraphQL framework package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 100 of 460)
| Version | Deps | Published |
|---|---|---|
| 1.8.235 | 5 / 2 | |
| 1.8.234 | 5 / 2 | |
| 1.8.233 | 5 / 2 | |
| 1.8.232 | 5 / 2 | |
| 1.8.231 | 5 / 2 | |
| 1.8.230 | 5 / 2 | |
| 1.8.229 | 5 / 2 | |
| 1.8.228 | 5 / 2 | |
| 1.8.227 | 5 / 2 | |
| 1.8.226 | 5 / 2 | |
| 1.8.225 | 5 / 2 | |
| 1.8.224 | 5 / 2 | |
| 1.8.223 | 5 / 2 | |
| 1.8.222 | 5 / 2 | |
| 1.8.221 | 5 / 2 | |
| 1.8.220 | 5 / 2 | |
| 1.8.219 | 5 / 2 | |
| 1.8.218 | 5 / 2 | |
| 1.8.217 | 5 / 2 | |
| 1.8.216 | 5 / 2 | |
| 1.8.215 | 5 / 2 | |
| 1.8.214 | 5 / 2 | |
| 1.8.213 | 5 / 2 | |
| 1.8.212 | 5 / 2 | |
| 1.8.211 | 5 / 2 | |
| 1.8.210 | 5 / 2 | |
| 1.8.209 | 5 / 2 | |
| 1.8.208 | 5 / 2 | |
| 1.8.207 | 5 / 2 | |
| 1.8.206 | 5 / 2 | |
| 1.8.205 | 5 / 2 | |
| 1.8.204 | 5 / 2 | |
| 1.8.203 | 5 / 2 | |
| 1.8.202 | 5 / 2 | |
| 1.8.201 | 5 / 2 | |
| 1.8.200 | 5 / 2 | |
| 1.8.199 | 5 / 2 | |
| 1.8.198 | 5 / 2 | |
| 1.8.197 | 5 / 2 | |
| 1.8.196 | 5 / 2 | |
| 1.8.195 | 5 / 2 | |
| 1.8.194 | 5 / 2 | |
| 1.8.193 | 5 / 2 | |
| 1.8.192 | 5 / 2 | |
| 1.8.191 | 5 / 2 | |
| 1.8.190 | 5 / 2 | |
| 1.8.189 | 5 / 2 | |
| 1.8.188 | 5 / 2 | |
| 1.8.187 | 5 / 2 | |
| 1.8.186 | 5 / 2 | |
| 1.8.185 | 5 / 2 | |
| 1.8.184 | 5 / 2 | |
| 1.8.183 | 5 / 2 | |
| 1.8.182 | 5 / 2 | |
| 1.8.181 | 5 / 2 | |
| 1.8.180 | 6 / 2 | |
| 1.8.179 | 6 / 2 | |
| 1.8.152 | 8 / 2 | |
| 1.8.150 | 8 / 2 | |
| 1.8.149 | 8 / 2 | |
| 1.8.148 | 8 / 2 | |
| 1.8.147 | 8 / 2 | |
| 1.8.146 | 8 / 2 | |
| 1.8.145 | 8 / 2 | |
| 1.8.144 | 8 / 2 | |
| 1.8.143 | 8 / 2 | |
| 1.8.142 | 8 / 2 | |
| 1.8.141 | 8 / 2 | |
| 1.8.140 | 8 / 2 | |
| 1.8.139 | 8 / 2 | |
| 1.8.138 | 8 / 2 | |
| 1.8.137 | 8 / 2 | |
| 1.8.136 | 8 / 2 | |
| 1.8.135 | 8 / 2 | |
| 1.8.134 | 8 / 2 | |
| 1.8.133 | 8 / 2 | |
| 1.8.132 | 8 / 2 | |
| 1.8.131 | 8 / 2 | |
| 1.8.130 | 8 / 2 | |
| 1.8.129 | 8 / 2 | |
| 1.8.128 | 8 / 2 | |
| 1.8.127 | 8 / 2 | |
| 1.8.126 | 8 / 2 | |
| 1.8.125 | 8 / 2 | |
| 1.8.124 | 8 / 2 | |
| 1.8.123 | 8 / 2 | |
| 1.8.122 | 8 / 2 | |
| 1.8.121 | 8 / 2 | |
| 1.8.120 | 8 / 2 | |
| 1.8.119 | 8 / 2 | |
| 1.8.118 | 8 / 2 | |
| 1.8.117 | 8 / 2 | |
| 1.8.116 | 8 / 2 | |
| 1.8.115 | 8 / 2 | |
| 1.8.114 | 8 / 2 | |
| 1.8.113 | 8 / 2 | |
| 1.8.112 | 8 / 2 | |
| 1.8.111 | 8 / 2 | |
| 1.8.110 | 8 / 2 | |
| 1.8.109 | 8 / 2 |
v1.8.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.