@teambit/component.ui.component-filters.env-filter
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for this package. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.0.282 | 8 / 8 | |
| 0.0.281 | 8 / 8 | |
| 0.0.280 | 8 / 8 | |
| 0.0.279 | 8 / 8 | |
| 0.0.278 | 8 / 8 | |
| 0.0.277 | 8 / 8 | |
| 0.0.276 | 8 / 8 | |
| 0.0.275 | 8 / 8 | |
| 0.0.274 | 8 / 8 | |
| 0.0.273 | 8 / 8 | |
| 0.0.272 | 8 / 8 | |
| 0.0.271 | 8 / 8 | |
| 0.0.270 | 8 / 8 | |
| 0.0.269 | 8 / 8 | |
| 0.0.268 | 8 / 8 | |
| 0.0.267 | 8 / 8 | |
| 0.0.266 | 8 / 8 | |
| 0.0.265 | 8 / 8 | |
| 0.0.264 | 8 / 8 | |
| 0.0.263 | 8 / 8 | |
| 0.0.262 | 8 / 8 | |
| 0.0.261 | 8 / 8 | |
| 0.0.260 | 8 / 8 | |
| 0.0.258 | 8 / 8 | |
| 0.0.257 | 8 / 8 | |
| 0.0.256 | 8 / 8 | |
| 0.0.255 | 8 / 8 | |
| 0.0.254 | 8 / 8 | |
| 0.0.253 | 8 / 8 | |
| 0.0.252 | 8 / 8 | |
| 0.0.250 | 8 / 8 | |
| 0.0.249 | 8 / 8 | |
| 0.0.248 | 8 / 8 | |
| 0.0.247 | 8 / 8 | |
| 0.0.246 | 8 / 8 | |
| 0.0.245 | 8 / 8 | |
| 0.0.244 | 8 / 8 | |
| 0.0.243 | 8 / 8 | |
| 0.0.242 | 8 / 8 | |
| 0.0.241 | 8 / 8 | |
| 0.0.240 | 8 / 8 | |
| 0.0.239 | 8 / 8 | |
| 0.0.238 | 8 / 8 | |
| 0.0.237 | 8 / 8 | |
| 0.0.236 | 8 / 8 | |
| 0.0.235 | 8 / 8 | |
| 0.0.234 | 8 / 8 | |
| 0.0.233 | 8 / 8 | |
| 0.0.231 | 8 / 8 | |
| 0.0.230 | 8 / 8 | |
| 0.0.229 | 8 / 8 |
v0.0.282
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.281
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.280
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.278
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.252
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (teambit-owner) than the most recent previously approved version (davidfirst) on 2025-04-16, but teambit-owner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.246
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.231
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.