@teambit/ui-foundation.ui.react-router.use-query
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/base-react.navigation.link | AI (dependencies): Official @teambit first-party package, not an unvetted dependency. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages routinely omit descriptions; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established teambit org package; lack of provenance is consistent across their releases. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.505 | 1 / 2 | |
| 0.0.504 | 1 / 2 | |
| 0.0.503 | 1 / 2 | |
| 0.0.502 | 0 / 2 |
v0.0.504
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 (shohamgilad) on 2024-05-08, 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.503
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.502
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.