@platforma-sdk/test
Typescript Block Test Helpers
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:@platforma-sdk/model | AI (phantom-deps): Same org scope; used transitively/via config in this SDK package. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): eslint loaded via config convention, not direct import; stable pattern for this tooling package. | ai | |
| phantom-deps | phantom-dep:@milaboratories/eslint-config | AI (phantom-deps): ESLint config plugin loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@milaboratories/ts-helpers | AI (phantom-deps): Referenced in config files; phantom-dep false positive for this SDK package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped SDK package with 747 versions; not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped SDK package; not a typosquat of next. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped SDK package; vitest is a declared dependency, not a target. | ai | |
| phantom-deps | phantom-dep:@vitest/coverage-istanbul | AI (phantom-deps): Coverage plugin loaded by vitest convention, not direct import; stable false positive. | ai |
Versions (showing 100 of 415)
| Version | Deps | Published |
|---|---|---|
| 1.39.7 | 7 / 4 | |
| 1.39.6 | 7 / 4 | |
| 1.39.5 | 7 / 4 | |
| 1.39.4 | 7 / 4 | |
| 1.39.2 | 7 / 4 | |
| 1.39.1 | 7 / 4 | |
| 1.39.0 | 7 / 4 | |
| 1.38.0 | 7 / 4 | |
| 1.37.19 | 7 / 4 | |
| 1.37.18 | 7 / 4 | |
| 1.37.17 | 7 / 4 | |
| 1.37.16 | 7 / 4 | |
| 1.37.14 | 7 / 4 | |
| 1.37.11 | 7 / 4 | |
| 1.37.9 | 7 / 4 | |
| 1.37.8 | 7 / 4 | |
| 1.37.6 | 7 / 4 | |
| 1.37.5 | 7 / 4 | |
| 1.37.3 | 7 / 4 | |
| 1.37.2 | 7 / 4 | |
| 1.37.0 | 7 / 4 | |
| 1.36.1 | 7 / 4 | |
| 1.35.4 | 7 / 4 | |
| 1.35.3 | 7 / 4 | |
| 1.35.1 | 7 / 4 | |
| 1.34.19 | 7 / 4 | |
| 1.34.18 | 7 / 4 | |
| 1.34.17 | 7 / 4 | |
| 1.34.16 | 7 / 4 | |
| 1.34.14 | 7 / 4 | |
| 1.34.13 | 7 / 4 | |
| 1.34.11 | 7 / 4 | |
| 1.34.10 | 7 / 4 | |
| 1.34.8 | 7 / 4 | |
| 1.34.7 | 7 / 4 | |
| 1.34.6 | 7 / 4 | |
| 1.34.5 | 7 / 4 | |
| 1.34.3 | 7 / 4 | |
| 1.34.2 | 7 / 4 | |
| 1.34.1 | 7 / 4 | |
| 1.34.0 | 7 / 4 | |
| 1.33.17 | 7 / 4 | |
| 1.33.16 | 7 / 4 | |
| 1.33.15 | 7 / 4 | |
| 1.33.14 | 7 / 4 | |
| 1.33.11 | 7 / 4 | |
| 1.33.10 | 7 / 4 | |
| 1.33.8 | 7 / 4 | |
| 1.33.5 | 7 / 4 | |
| 1.33.4 | 7 / 4 | |
| 1.33.2 | 7 / 4 | |
| 1.32.11 | 7 / 4 | |
| 1.32.10 | 7 / 4 | |
| 1.32.9 | 7 / 4 | |
| 1.32.8 | 7 / 4 | |
| 1.32.7 | 7 / 4 | |
| 1.32.6 | 7 / 4 | |
| 1.32.5 | 7 / 4 | |
| 1.32.4 | 7 / 4 | |
| 1.32.3 | 7 / 4 | |
| 1.32.2 | 7 / 4 | |
| 1.32.1 | 7 / 4 | |
| 1.31.18 | 7 / 4 | |
| 1.31.17 | 7 / 4 | |
| 1.31.16 | 7 / 4 | |
| 1.31.15 | 7 / 4 | |
| 1.31.14 | 7 / 4 | |
| 1.31.13 | 7 / 4 | |
| 1.31.12 | 7 / 4 | |
| 1.31.11 | 7 / 4 | |
| 1.31.10 | 7 / 4 | |
| 1.31.9 | 7 / 4 | |
| 1.31.8 | 7 / 4 | |
| 1.31.7 | 7 / 4 | |
| 1.31.6 | 7 / 4 | |
| 1.31.5 | 7 / 4 | |
| 1.31.4 | 7 / 4 | |
| 1.31.3 | 7 / 4 | |
| 1.30.39 | 7 / 4 | |
| 1.30.37 | 7 / 4 | |
| 1.30.36 | 7 / 4 | |
| 1.30.35 | 7 / 4 | |
| 1.30.34 | 7 / 4 | |
| 1.30.33 | 7 / 4 | |
| 1.30.32 | 7 / 4 | |
| 1.30.31 | 7 / 4 | |
| 1.30.30 | 7 / 4 | |
| 1.30.29 | 7 / 4 | |
| 1.30.28 | 7 / 4 | |
| 1.30.27 | 7 / 4 | |
| 1.30.26 | 7 / 4 | |
| 1.30.24 | 7 / 4 | |
| 1.30.21 | 7 / 4 | |
| 1.30.19 | 7 / 4 | |
| 1.30.18 | 7 / 4 | |
| 1.30.16 | 7 / 4 | |
| 1.30.14 | 7 / 4 | |
| 1.30.12 | 7 / 4 | |
| 1.30.11 | 7 / 4 | |
| 1.30.9 | 7 / 4 |
v1.39.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.