@teambit/toolbox.path.is-path-inside
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 consistently omit descriptions; stable false positive for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance across all their packages; stable pattern. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.0.512 | 1 / 3 | |
| 0.0.511 | 1 / 3 | |
| 0.0.510 | 1 / 3 | |
| 0.0.509 | 1 / 3 | |
| 0.0.508 | 1 / 3 | |
| 0.0.507 | 1 / 3 | |
| 0.0.506 | 1 / 3 | |
| 0.0.505 | 1 / 3 | |
| 0.0.504 | 1 / 3 | |
| 0.0.503 | 1 / 3 | |
| 0.0.502 | 1 / 3 | |
| 0.0.501 | 1 / 3 | |
| 0.0.500 | 1 / 3 | |
| 0.0.499 | 1 / 3 | |
| 0.0.498 | 1 / 3 | |
| 0.0.497 | 1 / 4 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.500
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.499
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.498
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.497
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.