@zthun/pokedex-api
An API backend for pokedexii that allows complex queries and faster load times.
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:rxjs | AI (phantom-deps): rxjs is a standard NestJS peer/implicit dep; not directly imported but required at runtime. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a well-known NestJS/TypeScript decorator runtime requirement. | ai | |
| phantom-deps | phantom-dep:@nestjs/platform-express | AI (phantom-deps): NestJS platform adapter; referenced in config, not directly imported — standard pattern. | ai | |
| phantom-deps | phantom-dep:@zthun/lumberjacky-log | AI (phantom-deps): Same-org logging package; indirect usage via lumberjacky-nest is expected. | ai | |
| phantom-deps | phantom-dep:@zthun/lumberjacky-nest | AI (phantom-deps): Same-org NestJS logging integration; phantom detection is a false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 19 / 10 | |
| 2.1.0 | 19 / 10 | |
| 2.0.11 | 19 / 10 | |
| 2.0.10 | 19 / 10 | |
| 2.0.9 | 19 / 10 | |
| 2.0.8 | 19 / 9 | |
| 2.0.7 | 19 / 9 | |
| 2.0.6 | 19 / 9 | |
| 2.0.5 | 19 / 9 | |
| 2.0.4 | 19 / 9 | |
| 2.0.3 | 19 / 9 | |
| 2.0.2 | 19 / 9 | |
| 2.0.1 | 19 / 9 | |
| 2.0.0 | 19 / 9 |
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.