@ledgerhq/revault-api
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/app-lib-6m-C02zy.d.mts | AI (source-diff): Bundled TypeScript declaration rollup (.d.mts); long lines are generated type definitions, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:lib/app-lib-DiunclRj.d.mts | AI (source-diff): Bundled TypeScript declaration file (.d.mts); long lines are expected in rollup-generated type bundles, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/app-lib-DHAtTIST.d.mts | AI (source-diff): Bundled TypeScript declaration file (.d.mts); long lines are normal for generated type rollups, not executable obfuscation. | ai | |
| source-diff | obfuscated-file:lib/app-lib-C6UV7d5U.d.mts | AI (source-diff): Bundled TypeScript declaration rollup; long lines in .d.mts are expected and carry no executable risk. | ai | |
| phantom-deps | phantom-dep:node-rsa | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:@fastify/cors | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:configcat-node | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:fastify-socket.io | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger-ui | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs prisma generate + openapi-ts codegen; standard for this backend API package across versions. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Monorepo package; deps declared for consumers, not all directly imported in lib output. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:bullmq | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:ioredis | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:dd-trace | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:elliptic | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:superjson | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Same monorepo pattern — stable false positive. | ai | |
| phantom-deps | phantom-dep:trpc-to-openapi | AI (phantom-deps): Declared dependency used in config/re-exports; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with minimal main entry; empty description and metadata are expected for internal APIs. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): Declared dependency used in config/re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): Declared dependency used in config/re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@trpc/server | AI (phantom-deps): Declared dependency used in config/re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared dependency used in type definitions and re-exported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:socket.io | AI (phantom-deps): Declared dependency used in config/re-exports; stable pattern for this package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 1.62.0 | 7 / 0 | |
| 1.61.0 | 7 / 0 | |
| 1.60.1 | 7 / 0 | |
| 1.60.0 | 7 / 0 | |
| 1.59.0 | 7 / 0 | |
| 1.58.0 | 7 / 0 | |
| 1.57.0 | 7 / 0 | |
| 1.56.0 | 7 / 0 | |
| 1.55.1 | 7 / 0 | |
| 1.53.0 | 7 / 0 | |
| 1.52.0 | 7 / 0 | |
| 1.51.0 | 7 / 0 | |
| 1.50.0 | 7 / 0 | |
| 1.49.0 | 7 / 0 | |
| 1.48.0 | 7 / 0 | |
| 1.47.0 | 7 / 0 | |
| 1.46.1 | 7 / 0 | |
| 1.46.0 | 7 / 0 | |
| 1.45.0 | 7 / 0 | |
| 1.44.0 | 7 / 0 | |
| 1.43.2 | 7 / 0 | |
| 1.43.1 | 8 / 0 | |
| 1.43.0 | 8 / 0 | |
| 1.42.0 | 8 / 0 | |
| 1.41.0 | 8 / 0 | |
| 1.40.2 | 8 / 0 | |
| 1.40.1 | 8 / 0 | |
| 1.40.0 | 8 / 0 | |
| 1.39.1 | 8 / 0 | |
| 1.39.0 | 8 / 0 | |
| 1.38.0 | 8 / 0 | |
| 1.37.1 | 8 / 0 | |
| 1.37.0 | 8 / 0 | |
| 1.36.0 | 8 / 0 | |
| 1.35.0 | 8 / 0 | |
| 1.34.0 | 8 / 0 | |
| 1.33.0 | 8 / 0 | |
| 1.32.1 | 8 / 0 | |
| 1.32.0 | 8 / 0 | |
| 1.31.0 | 8 / 0 | |
| 1.30.0 | 8 / 0 | |
| 1.29.4 | 8 / 0 | |
| 1.29.3 | 8 / 0 | |
| 1.29.2 | 8 / 0 | |
| 1.29.1 | 8 / 0 | |
| 1.29.0 | 8 / 0 | |
| 1.28.0 | 8 / 0 | |
| 1.23.1 | 8 / 0 | |
| 1.21.0 | 8 / 0 | |
| 1.20.0 | 32 / 31 |
v1.62.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
2 findingsScript: pnpm run prisma:generate && (openapi-ts -f src/tradelink/tradelink-openapi-client/openapi-ts.config.ts || true)
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.