@tramvai/module-render
Module for rendering React application on the server and in the browser
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance is a best-practice recommendation, not a blocker. | ai | |
| dependencies | unvetted-dep:@tinkoff/htmlpagebuilder | AI (dependencies): @tinkoff/* packages are first-party dependencies of this tramvai/tinkoff ecosystem package; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@tinkoff/request-plugin-protocol-http | AI (dependencies): @tinkoff/* packages are first-party dependencies of this tramvai/tinkoff ecosystem package; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is an intentional runtime dep replacement for node-fetch; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@tinkoff/user-agent | AI (phantom-deps): Declared runtime dep used by convention in tramvai framework; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/loadable__server | AI (phantom-deps): Type-only package loaded by TypeScript convention; not directly imported at runtime. | ai |
Versions (showing 12 of 114)
| Version | Deps | Published |
|---|---|---|
| 5.53.140 | 16 / 1 | |
| 5.53.123 | 16 / 1 | |
| 5.53.122 | 16 / 1 | |
| 5.53.120 | 16 / 1 | |
| 5.53.118 | 16 / 1 | |
| 5.53.117 | 16 / 1 | |
| 5.53.116 | 16 / 1 | |
| 5.53.115 | 16 / 1 | |
| 5.53.114 | 16 / 1 | |
| 5.53.112 | 16 / 1 | |
| 5.53.111 | 16 / 1 | |
| 5.53.94 | 16 / 1 |
v5.53.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.53.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.