@teambit/component.modules.component-url
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages routinely omit descriptions; not a malice indicator for this org. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is consistent across all teambit releases. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.0.187 | 3 / 4 | |
| 0.0.186 | 3 / 4 | |
| 0.0.185 | 3 / 4 | |
| 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.174 | 3 / 4 | |
| 0.0.173 | 3 / 4 | |
| 0.0.172 | 3 / 4 | |
| 0.0.171 | 3 / 6 | |
| 0.0.170 | 3 / 7 | |
| 0.0.169 | 3 / 7 | |
| 0.0.168 | 3 / 7 |
v0.0.176
2 findings[Accepted risk] Package 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.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.171
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidfirst) than the most recent previously approved version (teambit-owner) on 2025-01-12, but davidfirst 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.170
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidfirst) than the most recent previously approved version (teambit-owner) on 2024-12-10, but davidfirst 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.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.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.