@nsshunt/ststestrunner
STS Test Runner Module
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:http-status-codes | AI (phantom-deps): Imported indirectly through config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:fast-json-patch | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nsshunt/stsauthclient | AI (phantom-deps): Same-org internal dependency; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@nsshunt/stssocketioutils | AI (phantom-deps): Same-org internal dependency; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Directly imported in source; heuristic false positive. | ai |
Versions (showing 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 1.1.108 | 11 / 11 | |
| 1.1.107 | 11 / 11 | |
| 1.1.106 | 11 / 11 | |
| 1.1.105 | 10 / 11 | |
| 1.1.104 | 10 / 11 | |
| 1.1.103 | 10 / 11 | |
| 1.1.102 | 10 / 11 | |
| 1.1.101 | 10 / 11 | |
| 1.1.100 | 10 / 11 | |
| 1.1.99 | 10 / 11 | |
| 1.1.98 | 10 / 11 | |
| 1.1.97 | 10 / 11 | |
| 1.1.96 | 10 / 11 | |
| 1.1.95 | 10 / 11 | |
| 1.1.94 | 10 / 11 | |
| 1.1.93 | 10 / 11 | |
| 1.1.92 | 10 / 11 | |
| 1.1.91 | 10 / 11 | |
| 1.1.90 | 10 / 11 | |
| 1.1.89 | 10 / 11 | |
| 1.1.88 | 10 / 11 | |
| 1.1.87 | 10 / 11 | |
| 1.1.86 | 10 / 11 | |
| 1.1.85 | 10 / 11 | |
| 1.1.84 | 10 / 11 | |
| 1.1.83 | 10 / 11 | |
| 1.1.82 | 10 / 11 | |
| 1.1.81 | 10 / 11 | |
| 1.1.80 | 10 / 11 | |
| 1.1.79 | 10 / 11 | |
| 1.1.78 | 10 / 11 | |
| 1.1.77 | 10 / 11 | |
| 1.1.76 | 10 / 11 | |
| 1.1.75 | 10 / 11 | |
| 1.1.74 | 10 / 11 | |
| 1.1.73 | 10 / 11 | |
| 1.1.72 | 10 / 11 | |
| 1.1.71 | 10 / 11 | |
| 1.1.70 | 10 / 11 | |
| 1.1.69 | 10 / 11 | |
| 1.1.67 | 10 / 11 | |
| 1.1.66 | 10 / 11 | |
| 1.1.65 | 10 / 11 | |
| 1.1.64 | 10 / 11 | |
| 1.1.63 | 10 / 11 | |
| 1.1.62 | 10 / 11 | |
| 1.1.61 | 10 / 11 | |
| 1.1.60 | 10 / 11 | |
| 1.1.59 | 10 / 11 | |
| 1.1.58 | 10 / 11 | |
| 1.1.57 | 10 / 11 | |
| 1.1.56 | 10 / 11 | |
| 1.1.55 | 10 / 11 | |
| 1.1.54 | 10 / 11 | |
| 1.1.53 | 10 / 11 | |
| 1.1.52 | 10 / 11 | |
| 1.1.51 | 10 / 11 | |
| 1.1.50 | 10 / 11 | |
| 1.1.49 | 10 / 11 | |
| 1.1.48 | 10 / 11 | |
| 1.1.47 | 10 / 11 | |
| 1.1.46 | 10 / 11 | |
| 1.1.45 | 10 / 11 | |
| 1.1.44 | 10 / 11 | |
| 1.1.43 | 10 / 11 | |
| 1.1.42 | 10 / 11 | |
| 1.1.41 | 11 / 11 | |
| 1.1.40 | 10 / 11 | |
| 1.1.39 | 8 / 11 | |
| 1.1.38 | 8 / 11 | |
| 1.1.37 | 10 / 11 | |
| 1.1.36 | 10 / 11 | |
| 1.1.35 | 8 / 11 | |
| 1.1.34 | 8 / 11 | |
| 1.1.33 | 8 / 11 | |
| 1.1.32 | 8 / 11 | |
| 1.1.31 | 8 / 11 | |
| 1.1.30 | 8 / 11 | |
| 1.1.29 | 8 / 11 | |
| 1.1.28 | 8 / 11 | |
| 1.1.27 | 8 / 11 | |
| 1.1.26 | 8 / 11 | |
| 1.1.25 | 8 / 11 | |
| 1.1.24 | 8 / 11 | |
| 1.1.23 | 8 / 11 | |
| 1.1.22 | 8 / 11 | |
| 1.1.21 | 8 / 11 | |
| 1.1.20 | 8 / 11 | |
| 1.1.19 | 8 / 11 | |
| 1.1.18 | 8 / 11 | |
| 1.1.17 | 8 / 11 | |
| 1.1.16 | 8 / 11 | |
| 1.1.15 | 8 / 11 | |
| 1.1.14 | 8 / 11 | |
| 1.1.13 | 8 / 11 | |
| 1.1.12 | 8 / 11 | |
| 1.1.11 | 8 / 11 | |
| 1.1.10 | 8 / 11 | |
| 1.1.9 | 12 / 14 | |
| 1.1.8 | 12 / 14 |
v1.1.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.