@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.63.8 | 7 / 5 | |
| 1.63.7 | 7 / 5 | |
| 1.63.6 | 7 / 5 | |
| 1.63.5 | 7 / 5 | |
| 1.63.4 | 7 / 5 | |
| 1.63.3 | 7 / 5 | |
| 1.63.2 | 7 / 5 | |
| 1.63.1 | 7 / 5 | |
| 1.63.0 | 7 / 5 | |
| 1.62.1 | 7 / 5 | |
| 1.62.0 | 7 / 5 | |
| 1.61.5 | 6 / 5 | |
| 1.61.4 | 6 / 5 | |
| 1.58.22 | 6 / 5 | |
| 1.58.20 | 6 / 5 | |
| 1.58.19 | 6 / 5 | |
| 1.48.13 | 10 / 5 | |
| 1.48.12 | 7 / 5 | |
| 1.48.11 | 7 / 5 | |
| 1.48.9 | 7 / 5 | |
| 1.48.8 | 7 / 5 | |
| 1.48.7 | 7 / 5 | |
| 1.48.6 | 7 / 5 | |
| 1.48.5 | 7 / 5 | |
| 1.48.4 | 7 / 5 | |
| 1.48.3 | 7 / 5 | |
| 1.48.2 | 7 / 5 | |
| 1.48.1 | 7 / 5 | |
| 1.47.6 | 7 / 5 | |
| 1.47.5 | 7 / 5 | |
| 1.47.3 | 7 / 5 | |
| 1.47.2 | 7 / 5 | |
| 1.47.1 | 7 / 5 | |
| 1.46.5 | 7 / 5 | |
| 1.46.4 | 7 / 5 | |
| 1.46.3 | 7 / 5 | |
| 1.46.2 | 7 / 5 | |
| 1.46.0 | 7 / 5 | |
| 1.45.47 | 7 / 5 | |
| 1.45.46 | 7 / 5 | |
| 1.45.45 | 7 / 5 | |
| 1.45.44 | 7 / 5 | |
| 1.45.43 | 7 / 5 | |
| 1.45.42 | 7 / 5 | |
| 1.45.41 | 7 / 5 | |
| 1.45.40 | 7 / 5 | |
| 1.45.39 | 7 / 5 | |
| 1.45.38 | 7 / 5 | |
| 1.45.35 | 7 / 5 | |
| 1.45.33 | 7 / 5 | |
| 1.45.32 | 7 / 5 | |
| 1.45.30 | 7 / 5 | |
| 1.45.29 | 7 / 5 | |
| 1.45.27 | 7 / 5 | |
| 1.45.26 | 7 / 5 | |
| 1.45.25 | 7 / 5 | |
| 1.45.24 | 7 / 5 | |
| 1.45.23 | 7 / 5 | |
| 1.45.22 | 7 / 5 | |
| 1.45.21 | 7 / 5 | |
| 1.45.20 | 7 / 5 | |
| 1.45.19 | 7 / 5 | |
| 1.45.18 | 7 / 5 | |
| 1.45.17 | 7 / 5 | |
| 1.45.16 | 7 / 5 | |
| 1.45.15 | 7 / 5 | |
| 1.45.14 | 7 / 5 | |
| 1.45.12 | 7 / 5 | |
| 1.45.11 | 7 / 5 | |
| 1.45.10 | 7 / 5 | |
| 1.45.9 | 7 / 5 | |
| 1.45.8 | 7 / 5 | |
| 1.45.7 | 7 / 5 | |
| 1.45.6 | 7 / 5 | |
| 1.45.4 | 7 / 5 | |
| 1.45.3 | 7 / 5 | |
| 1.45.2 | 7 / 5 | |
| 1.45.1 | 7 / 5 | |
| 1.45.0 | 7 / 5 | |
| 1.44.22 | 7 / 5 | |
| 1.44.21 | 7 / 5 | |
| 1.44.20 | 7 / 5 | |
| 1.44.19 | 7 / 5 | |
| 1.44.18 | 7 / 5 | |
| 1.44.17 | 7 / 5 | |
| 1.44.16 | 7 / 5 | |
| 1.44.15 | 7 / 5 | |
| 1.44.14 | 7 / 5 | |
| 1.44.13 | 7 / 5 | |
| 1.44.12 | 7 / 5 | |
| 1.44.11 | 7 / 5 | |
| 1.44.10 | 7 / 5 | |
| 1.44.9 | 7 / 5 | |
| 1.44.8 | 7 / 5 | |
| 1.44.7 | 7 / 5 | |
| 1.44.6 | 7 / 5 | |
| 1.44.5 | 7 / 5 | |
| 1.44.4 | 7 / 5 | |
| 1.44.3 | 7 / 5 | |
| 1.44.1 | 7 / 5 |
v1.63.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.22
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.20
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.19
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.2
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.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.