@hed-hog/finance
Este documento técnico detalha o módulo financeiro `@hed-hog/finance` do monorepo HedHog, cobrindo sua visão geral, escopo, endpoints, regras de autenticação, estruturas de dados, erros comuns, banco de dados, regras de negócio e guia rápido de uso.
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard Buffer.from(fileBase64, 'base64') file-handling pattern; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@nestjs/core | AI (phantom-deps): NestJS framework dep declared for peer/config use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nestjs/mapped-types | AI (phantom-deps): NestJS framework dep declared for peer/config use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hed-hog/api | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@nestjs/jwt | AI (phantom-deps): NestJS framework dep declared for peer/config use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@hed-hog/contact | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@hed-hog/api-types | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@hed-hog/tag | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.353 | 13 / 0 | |
| 0.0.329 | 13 / 0 | |
| 0.0.225 | 12 / 0 | |
| 0.0.223 | 12 / 0 | |
| 0.0.3 | 12 / 0 |
v0.0.353
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.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.