@gapi/ac
The @gapi/ac library is an access control utility designed for use in GraphQL applications. It helps developers manage permissions for different user roles, such as GUEST, USER, and ADMIN, across various GraphQL actions like queries, mutations, subscripti
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @gapi package; Levenshtein match to 'pg' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @gapi package; Levenshtein match to 'qs' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @gapi package; Levenshtein match to 'ajv' is coincidental, not a typosquat. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 1.8.229 | 0 / 12 | |
| 1.8.228 | 0 / 12 | |
| 1.8.227 | 0 / 12 | |
| 1.8.226 | 0 / 12 | |
| 1.8.225 | 0 / 12 | |
| 1.8.224 | 0 / 12 | |
| 1.8.223 | 0 / 12 | |
| 1.8.222 | 0 / 12 | |
| 1.8.221 | 0 / 12 | |
| 1.8.220 | 0 / 12 | |
| 1.8.219 | 0 / 12 | |
| 1.8.218 | 0 / 12 | |
| 1.8.217 | 0 / 12 | |
| 1.8.216 | 0 / 12 | |
| 1.8.215 | 0 / 12 | |
| 1.8.214 | 0 / 12 | |
| 1.8.213 | 0 / 12 | |
| 1.8.212 | 0 / 12 | |
| 1.8.211 | 0 / 12 | |
| 1.8.210 | 0 / 12 | |
| 1.8.209 | 0 / 12 | |
| 1.8.208 | 0 / 12 | |
| 1.8.207 | 0 / 12 | |
| 1.8.206 | 0 / 12 | |
| 1.8.205 | 0 / 12 | |
| 1.8.204 | 0 / 12 | |
| 1.8.203 | 0 / 12 | |
| 1.8.202 | 0 / 12 | |
| 1.8.201 | 0 / 12 | |
| 1.8.200 | 0 / 12 | |
| 1.8.199 | 0 / 12 | |
| 1.8.198 | 0 / 12 | |
| 1.8.197 | 0 / 12 | |
| 1.8.196 | 0 / 12 | |
| 1.8.195 | 0 / 12 | |
| 1.8.194 | 0 / 12 | |
| 1.8.193 | 0 / 12 | |
| 1.8.192 | 0 / 12 | |
| 1.8.191 | 0 / 12 | |
| 1.8.190 | 0 / 12 | |
| 1.8.189 | 0 / 12 | |
| 1.8.188 | 0 / 12 | |
| 1.8.187 | 0 / 12 | |
| 1.8.186 | 0 / 12 | |
| 1.8.185 | 0 / 12 | |
| 1.8.184 | 0 / 12 | |
| 1.8.183 | 0 / 12 | |
| 1.8.182 | 0 / 12 | |
| 1.8.181 | 0 / 12 | |
| 1.8.180 | 0 / 12 | |
| 1.8.179 | 0 / 12 |
v1.8.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.