@teambit/workspace.modules.match-pattern
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages consistently omit descriptions; not a malware signal for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across all teambit packages; not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.521 | 5 / 6 | |
| 0.0.520 | 5 / 6 | |
| 0.0.519 | 5 / 6 | |
| 0.0.518 | 5 / 6 | |
| 0.0.517 | 5 / 6 | |
| 0.0.516 | 5 / 6 | |
| 0.0.515 | 5 / 6 | |
| 0.0.514 | 5 / 6 | |
| 0.0.513 | 5 / 6 | |
| 0.0.512 | 5 / 6 | |
| 0.0.511 | 5 / 6 | |
| 0.0.510 | 5 / 6 |
v0.0.521
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.519
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.518
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.517
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.516
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.515
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.514
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.513
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.512
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.511
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.510
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.