@teambit/component.ui.component-filters.component-filter-context
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): teambit-owner is the org account for teambit; transition from individual to org publisher is expected for this package family. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by org-account publish is consistent with a maintainer consolidation, not takeover. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit/polyfill dependency; phantom-dep false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.0.242 | 3 / 8 | |
| 0.0.241 | 3 / 8 | |
| 0.0.240 | 3 / 8 | |
| 0.0.239 | 3 / 8 | |
| 0.0.238 | 3 / 8 | |
| 0.0.237 | 3 / 8 | |
| 0.0.235 | 3 / 8 | |
| 0.0.234 | 3 / 8 | |
| 0.0.233 | 3 / 8 | |
| 0.0.232 | 3 / 8 | |
| 0.0.231 | 3 / 8 | |
| 0.0.230 | 3 / 8 | |
| 0.0.229 | 3 / 8 | |
| 0.0.227 | 3 / 8 | |
| 0.0.226 | 3 / 8 | |
| 0.0.225 | 3 / 8 | |
| 0.0.223 | 3 / 8 |
v0.0.237
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.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.232
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.