@teambit/workspace.testing.mock-workspace
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/legacy.e2e-helper | AI (dependencies): Internal teambit scoped dependency; consistent with the package's testing utility role within the teambit ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): davidfirst is a long-standing teambit org publisher (1791 days, 178 approved); transition appears legitimate. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Teambit org package; internal maintainer rotation is expected across 444 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped component package in teambit monorepo; missing description is a consistent pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established teambit package; no provenance is consistent across all versions in this ecosystem. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.0.184 | 3 / 4 | |
| 0.0.183 | 3 / 4 | |
| 0.0.182 | 3 / 4 | |
| 0.0.181 | 3 / 4 | |
| 0.0.180 | 3 / 4 | |
| 0.0.179 | 3 / 4 | |
| 0.0.178 | 3 / 4 | |
| 0.0.177 | 3 / 4 | |
| 0.0.176 | 3 / 4 | |
| 0.0.173 | 3 / 4 | |
| 0.0.172 | 3 / 4 | |
| 0.0.171 | 3 / 4 | |
| 0.0.170 | 3 / 4 | |
| 0.0.169 | 3 / 4 | |
| 0.0.167 | 3 / 4 | |
| 0.0.166 | 3 / 4 | |
| 0.0.165 | 3 / 4 | |
| 0.0.164 | 3 / 4 | |
| 0.0.163 | 3 / 4 | |
| 0.0.162 | 3 / 4 | |
| 0.0.161 | 3 / 4 | |
| 0.0.160 | 3 / 4 | |
| 0.0.159 | 3 / 4 | |
| 0.0.158 | 3 / 4 | |
| 0.0.157 | 3 / 4 | |
| 0.0.156 | 3 / 4 | |
| 0.0.155 | 3 / 4 | |
| 0.0.154 | 3 / 4 | |
| 0.0.153 | 3 / 4 | |
| 0.0.152 | 3 / 4 | |
| 0.0.150 | 3 / 4 | |
| 0.0.149 | 3 / 4 | |
| 0.0.148 | 3 / 4 | |
| 0.0.147 | 3 / 4 | |
| 0.0.146 | 3 / 4 | |
| 0.0.145 | 3 / 4 | |
| 0.0.144 | 3 / 4 | |
| 0.0.143 | 3 / 4 | |
| 0.0.140 | 3 / 4 | |
| 0.0.131 | 3 / 4 | |
| 0.0.129 | 3 / 4 | |
| 0.0.127 | 3 / 4 | |
| 0.0.126 | 3 / 4 | |
| 0.0.124 | 3 / 4 | |
| 0.0.122 | 3 / 4 | |
| 0.0.121 | 3 / 4 | |
| 0.0.119 | 3 / 4 | |
| 0.0.118 | 3 / 4 | |
| 0.0.116 | 3 / 4 | |
| 0.0.115 | 3 / 4 | |
| 0.0.111 | 3 / 4 | |
| 0.0.109 | 3 / 4 | |
| 0.0.107 | 3 / 4 | |
| 0.0.102 | 3 / 4 | |
| 0.0.101 | 3 / 4 | |
| 0.0.100 | 3 / 4 | |
| 0.0.99 | 3 / 4 | |
| 0.0.97 | 3 / 4 | |
| 0.0.94 | 3 / 4 | |
| 0.0.93 | 3 / 4 | |
| 0.0.92 | 3 / 4 | |
| 0.0.91 | 3 / 4 | |
| 0.0.90 | 3 / 4 | |
| 0.0.89 | 3 / 4 | |
| 0.0.88 | 3 / 4 | |
| 0.0.87 | 3 / 4 |
v0.0.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.182
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.181
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.179
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.152
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.150
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.149
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.148
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.147
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.146
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.145
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.144
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.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.
v0.0.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
2 findingsThis version was published by a different npm account than previous versions on 2025-07-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.