@hed-hog/faq
O módulo `@hed-hog/faq` é responsável pela gestão de FAQs (Frequently Asked Questions) multilíngues dentro do sistema HedHog. Ele permite criar, listar, atualizar, consultar e deletar FAQs com suporte a múltiplos idiomas, garantindo que cada pergunta e re
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@hed-hog/core | AI (phantom-deps): Same-org dependency used via framework module system, not direct import. | ai | |
| phantom-deps | phantom-dep:@nestjs/jwt | AI (phantom-deps): NestJS framework module; typical indirect reference pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): NestJS framework module; typical indirect reference pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@nestjs/config | AI (phantom-deps): NestJS framework module; typical indirect reference pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@nestjs/mapped-types | AI (phantom-deps): NestJS framework module; typical indirect reference pattern for this package type. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 0.0.347 | 10 / 0 | |
| 0.0.332 | 10 / 0 | |
| 0.0.331 | 10 / 0 | |
| 0.0.330 | 10 / 0 | |
| 0.0.329 | 10 / 0 | |
| 0.0.328 | 10 / 0 | |
| 0.0.327 | 10 / 0 | |
| 0.0.326 | 10 / 0 | |
| 0.0.325 | 10 / 0 | |
| 0.0.322 | 10 / 0 | |
| 0.0.319 | 10 / 0 | |
| 0.0.318 | 10 / 0 | |
| 0.0.317 | 10 / 0 | |
| 0.0.316 | 10 / 0 | |
| 0.0.314 | 10 / 0 | |
| 0.0.312 | 10 / 0 | |
| 0.0.311 | 10 / 0 | |
| 0.0.310 | 10 / 0 | |
| 0.0.309 | 10 / 0 | |
| 0.0.306 | 10 / 0 | |
| 0.0.305 | 10 / 0 | |
| 0.0.304 | 10 / 0 | |
| 0.0.303 | 10 / 0 | |
| 0.0.302 | 10 / 0 | |
| 0.0.301 | 10 / 0 | |
| 0.0.300 | 10 / 0 | |
| 0.0.299 | 10 / 0 | |
| 0.0.298 | 10 / 0 | |
| 0.0.297 | 10 / 0 | |
| 0.0.296 | 10 / 0 | |
| 0.0.295 | 10 / 0 | |
| 0.0.294 | 10 / 0 | |
| 0.0.293 | 10 / 0 | |
| 0.0.292 | 10 / 0 | |
| 0.0.291 | 10 / 0 | |
| 0.0.286 | 10 / 0 | |
| 0.0.285 | 10 / 0 | |
| 0.0.279 | 10 / 0 | |
| 0.0.278 | 10 / 0 | |
| 0.0.276 | 10 / 0 | |
| 0.0.275 | 10 / 0 | |
| 0.0.274 | 10 / 0 | |
| 0.0.273 | 10 / 0 | |
| 0.0.270 | 10 / 0 | |
| 0.0.266 | 10 / 0 | |
| 0.0.261 | 10 / 0 | |
| 0.0.258 | 10 / 0 | |
| 0.0.250 | 10 / 0 | |
| 0.0.249 | 10 / 0 | |
| 0.0.240 | 10 / 0 | |
| 0.0.239 | 10 / 0 | |
| 0.0.238 | 10 / 0 | |
| 0.0.237 | 10 / 0 | |
| 0.0.236 | 10 / 0 | |
| 0.0.235 | 10 / 0 | |
| 0.0.234 | 10 / 0 | |
| 0.0.233 | 10 / 0 | |
| 0.0.232 | 10 / 0 | |
| 0.0.222 | 10 / 0 | |
| 0.0.219 | 10 / 0 | |
| 0.0.216 | 10 / 0 | |
| 0.0.212 | 10 / 0 | |
| 0.0.197 | 10 / 0 | |
| 0.0.194 | 10 / 0 | |
| 0.0.193 | 10 / 0 | |
| 0.0.191 | 10 / 0 | |
| 0.0.190 | 10 / 0 | |
| 0.0.186 | 10 / 0 | |
| 0.0.185 | 10 / 0 | |
| 0.0.184 | 10 / 0 | |
| 0.0.183 | 10 / 0 | |
| 0.0.182 | 10 / 0 | |
| 0.0.163 | 10 / 0 | |
| 0.0.151 | 10 / 0 | |
| 0.0.143 | 10 / 0 | |
| 0.0.142 | 10 / 0 | |
| 0.0.141 | 10 / 0 | |
| 0.0.140 | 10 / 0 | |
| 0.0.139 | 10 / 0 | |
| 0.0.138 | 10 / 0 | |
| 0.0.137 | 10 / 0 | |
| 0.0.134 | 10 / 0 | |
| 0.0.131 | 10 / 0 | |
| 0.0.127 | 10 / 0 | |
| 0.0.124 | 10 / 0 | |
| 0.0.122 | 10 / 0 | |
| 0.0.115 | 10 / 0 | |
| 0.0.114 | 10 / 0 | |
| 0.0.104 | 10 / 0 | |
| 0.0.103 | 10 / 0 | |
| 0.0.102 | 10 / 0 | |
| 0.0.68 | 10 / 0 | |
| 0.0.67 | 10 / 0 |
v0.0.347
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.332
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.331
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.330
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.329
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.328
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.327
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.326
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.325
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.322
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.319
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.318
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.317
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.316
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.312
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.309
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.305
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.304
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.303
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.302
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.301
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.300
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.299
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.298
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.291
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.286
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.285
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.278
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.258
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.232
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.