@teambit/preview.ui.preview-placeholder
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a declared runtime polyfill dependency; phantom-dep false positive stable for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 0.0.575 | 4 / 7 | |
| 0.0.574 | 4 / 7 | |
| 0.0.573 | 4 / 7 | |
| 0.0.572 | 4 / 7 | |
| 0.0.571 | 4 / 7 | |
| 0.0.570 | 4 / 7 | |
| 0.0.569 | 4 / 7 | |
| 0.0.568 | 4 / 7 | |
| 0.0.567 | 4 / 7 | |
| 0.0.566 | 4 / 7 | |
| 0.0.565 | 4 / 7 | |
| 0.0.564 | 4 / 7 | |
| 0.0.563 | 5 / 7 | |
| 0.0.562 | 5 / 7 | |
| 0.0.561 | 5 / 7 | |
| 0.0.560 | 5 / 7 | |
| 0.0.559 | 5 / 7 | |
| 0.0.558 | 5 / 7 | |
| 0.0.557 | 5 / 7 | |
| 0.0.555 | 5 / 7 | |
| 0.0.554 | 5 / 7 | |
| 0.0.553 | 5 / 7 | |
| 0.0.552 | 5 / 7 | |
| 0.0.549 | 5 / 7 | |
| 0.0.548 | 5 / 7 | |
| 0.0.547 | 5 / 7 | |
| 0.0.546 | 5 / 7 | |
| 0.0.545 | 5 / 7 | |
| 0.0.543 | 5 / 7 | |
| 0.0.542 | 5 / 7 | |
| 0.0.540 | 5 / 7 | |
| 0.0.539 | 5 / 7 | |
| 0.0.538 | 5 / 7 | |
| 0.0.537 | 5 / 7 | |
| 0.0.536 | 5 / 7 | |
| 0.0.535 | 5 / 7 | |
| 0.0.534 | 5 / 7 | |
| 0.0.533 | 5 / 7 | |
| 0.0.532 | 5 / 7 | |
| 0.0.531 | 5 / 7 | |
| 0.0.530 | 5 / 7 | |
| 0.0.529 | 5 / 7 | |
| 0.0.528 | 5 / 7 | |
| 0.0.527 | 5 / 7 | |
| 0.0.526 | 5 / 7 | |
| 0.0.525 | 5 / 7 | |
| 0.0.524 | 5 / 7 | |
| 0.0.523 | 5 / 7 | |
| 0.0.522 | 5 / 7 | |
| 0.0.521 | 5 / 7 | |
| 0.0.520 | 5 / 7 |
v0.0.575
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.574
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.573
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.572
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.571
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.542
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 (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.540
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.539
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.538
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.537
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.536
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.535
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.534
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.533
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.532
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.531
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.530
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.529
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.528
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.525
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.524
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.523
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.522
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.521
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.520
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.