@teambit/component.ui.component-filters.deprecate-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): davidfirst is a long-standing teambit publisher with 206 approved packages; transition is consistent with org account management. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by publisher change aligns with org-level account migration, not takeover; no code changes introduced. | ai | |
| 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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.0.244 | 4 / 8 | |
| 0.0.243 | 4 / 8 | |
| 0.0.242 | 4 / 8 | |
| 0.0.241 | 4 / 8 | |
| 0.0.240 | 4 / 8 | |
| 0.0.239 | 4 / 8 | |
| 0.0.238 | 4 / 8 | |
| 0.0.237 | 4 / 8 | |
| 0.0.236 | 4 / 8 | |
| 0.0.235 | 4 / 8 | |
| 0.0.233 | 4 / 8 | |
| 0.0.232 | 4 / 8 | |
| 0.0.231 | 4 / 8 | |
| 0.0.230 | 4 / 8 | |
| 0.0.229 | 4 / 8 | |
| 0.0.228 | 4 / 8 | |
| 0.0.227 | 4 / 8 | |
| 0.0.226 | 4 / 8 | |
| 0.0.225 | 4 / 8 | |
| 0.0.224 | 4 / 8 | |
| 0.0.223 | 4 / 8 | |
| 0.0.221 | 4 / 8 |
v0.0.235
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.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.228
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.224
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.