@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 414)
| Version | Deps | Published |
|---|---|---|
| 1.43.19 | 7 / 5 | |
| 1.43.18 | 7 / 5 | |
| 1.43.17 | 7 / 5 | |
| 1.43.16 | 7 / 5 | |
| 1.43.15 | 7 / 5 | |
| 1.43.14 | 7 / 5 | |
| 1.43.13 | 7 / 5 | |
| 1.43.12 | 7 / 5 | |
| 1.43.11 | 7 / 5 | |
| 1.43.10 | 7 / 5 | |
| 1.43.9 | 7 / 5 | |
| 1.43.8 | 7 / 5 | |
| 1.43.7 | 7 / 5 | |
| 1.43.6 | 7 / 5 | |
| 1.43.5 | 7 / 5 | |
| 1.43.4 | 7 / 5 | |
| 1.43.3 | 7 / 5 | |
| 1.43.2 | 7 / 5 | |
| 1.43.0 | 7 / 5 | |
| 1.42.55 | 7 / 5 | |
| 1.42.54 | 7 / 5 | |
| 1.42.53 | 7 / 5 | |
| 1.42.52 | 7 / 5 | |
| 1.42.51 | 7 / 5 | |
| 1.42.50 | 7 / 5 | |
| 1.42.49 | 7 / 5 | |
| 1.42.48 | 7 / 5 | |
| 1.42.47 | 7 / 5 | |
| 1.42.46 | 7 / 5 | |
| 1.42.45 | 7 / 5 | |
| 1.42.44 | 7 / 5 | |
| 1.42.43 | 7 / 5 | |
| 1.42.42 | 7 / 5 | |
| 1.42.41 | 7 / 5 | |
| 1.42.40 | 7 / 5 | |
| 1.42.39 | 7 / 5 | |
| 1.42.38 | 7 / 5 | |
| 1.42.37 | 7 / 5 | |
| 1.42.36 | 7 / 5 | |
| 1.42.35 | 7 / 5 | |
| 1.42.33 | 7 / 5 | |
| 1.42.32 | 7 / 5 | |
| 1.42.31 | 7 / 5 | |
| 1.42.30 | 7 / 5 | |
| 1.42.29 | 7 / 5 | |
| 1.42.28 | 7 / 5 | |
| 1.42.27 | 7 / 5 | |
| 1.42.20 | 7 / 5 | |
| 1.42.17 | 7 / 4 | |
| 1.42.15 | 7 / 4 | |
| 1.42.13 | 7 / 4 | |
| 1.42.12 | 7 / 4 | |
| 1.42.11 | 7 / 4 | |
| 1.42.10 | 7 / 4 | |
| 1.42.9 | 7 / 4 | |
| 1.42.8 | 7 / 4 | |
| 1.42.7 | 7 / 4 | |
| 1.42.6 | 7 / 4 | |
| 1.42.4 | 7 / 4 | |
| 1.42.1 | 7 / 4 | |
| 1.42.0 | 7 / 4 | |
| 1.41.18 | 7 / 4 | |
| 1.41.16 | 7 / 4 | |
| 1.41.15 | 7 / 4 | |
| 1.41.14 | 7 / 4 | |
| 1.41.12 | 7 / 4 | |
| 1.41.10 | 7 / 4 | |
| 1.41.8 | 7 / 4 | |
| 1.41.7 | 7 / 4 | |
| 1.41.6 | 7 / 4 | |
| 1.41.5 | 7 / 4 | |
| 1.41.4 | 7 / 4 | |
| 1.41.3 | 7 / 4 | |
| 1.41.2 | 7 / 4 | |
| 1.41.1 | 7 / 4 | |
| 1.41.0 | 7 / 4 | |
| 1.40.6 | 7 / 4 | |
| 1.40.5 | 7 / 4 | |
| 1.40.1 | 7 / 4 | |
| 1.40.0 | 7 / 4 | |
| 1.39.21 | 7 / 4 | |
| 1.39.19 | 7 / 4 | |
| 1.39.18 | 7 / 4 | |
| 1.39.15 | 7 / 4 | |
| 1.39.14 | 7 / 4 | |
| 1.39.13 | 7 / 4 | |
| 1.39.12 | 7 / 4 | |
| 1.39.11 | 7 / 4 | |
| 1.39.9 | 7 / 4 | |
| 1.39.8 | 7 / 4 | |
| 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 |
v1.43.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.1
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.5
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.