@teambit/ui-foundation.ui.react-router.slot-router
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 first-party @teambit package, not unvetted. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.0.527 | 3 / 8 | |
| 0.0.526 | 2 / 3 | |
| 0.0.525 | 2 / 3 | |
| 0.0.524 | 2 / 3 | |
| 0.0.523 | 2 / 3 | |
| 0.0.522 | 2 / 3 | |
| 0.0.521 | 2 / 3 | |
| 0.0.520 | 2 / 3 | |
| 0.0.519 | 2 / 3 | |
| 0.0.518 | 2 / 3 | |
| 0.0.517 | 2 / 3 | |
| 0.0.516 | 2 / 3 | |
| 0.0.515 | 2 / 3 | |
| 0.0.514 | 3 / 3 | |
| 0.0.513 | 2 / 3 | |
| 0.0.512 | 2 / 3 | |
| 0.0.511 | 2 / 3 | |
| 0.0.510 | 2 / 3 | |
| 0.0.509 | 2 / 3 |
v0.0.527
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.526
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.516
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.515
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.514
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 (shohamgilad) than the most recent previously approved version (davidfirst) on 2025-02-09, but shohamgilad 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.513
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.512
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.511
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.510
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.509
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.