@tramvai/module-mocker
Module uses library [@tinkoff/mocker](references/libs/mocker.md) to add a mocker functionality to the `tramvai` app. Mocker will be available as [papi](references/modules/server.md#papi) route with path `/mocker`.
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): Large monorepo package; provenance not historically published for this ecosystem. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 5.53.140 | 2 / 0 | |
| 5.53.123 | 2 / 0 | |
| 5.53.122 | 2 / 0 | |
| 5.53.120 | 2 / 0 | |
| 5.53.118 | 2 / 0 | |
| 5.53.117 | 2 / 0 | |
| 5.53.116 | 2 / 0 | |
| 5.53.115 | 2 / 0 | |
| 5.53.114 | 2 / 0 | |
| 5.53.112 | 2 / 0 | |
| 5.53.111 | 2 / 0 | |
| 5.53.94 | 2 / 0 |
v5.53.140
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.