@teambit/defender.ui.test-page
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org @teambit package, low supply-chain risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher is a known maintainer of this org's packages; routine roster change. | ai | |
| dependencies | unvetted-dep:@teambit/design.content.table | AI (dependencies): Sibling @teambit scoped package from the same trusted publisher ecosystem; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): teambit-owner is the org-level publisher for the teambit ecosystem; transition from individual davidfirst to org account is expected. | ai | |
| provenance | no-provenance | AI (provenance): Established teambit publisher; lack of provenance is consistent across all their packages. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill runtime dep; phantom-dep false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Component-scoped package from teambit; missing description is a stable pattern for their component packages. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.0.87 | 13 / 8 | |
| 0.0.84 | 13 / 8 | |
| 0.0.83 | 13 / 8 | |
| 0.0.82 | 13 / 8 | |
| 0.0.81 | 13 / 8 | |
| 0.0.80 | 13 / 8 | |
| 0.0.79 | 13 / 8 | |
| 0.0.78 | 13 / 8 | |
| 0.0.77 | 13 / 8 | |
| 0.0.76 | 13 / 8 | |
| 0.0.75 | 13 / 8 | |
| 0.0.74 | 13 / 8 | |
| 0.0.73 | 13 / 8 | |
| 0.0.72 | 13 / 8 | |
| 0.0.67 | 13 / 8 | |
| 0.0.66 | 13 / 8 | |
| 0.0.65 | 13 / 8 | |
| 0.0.64 | 13 / 8 | |
| 0.0.63 | 13 / 8 | |
| 0.0.62 | 13 / 8 | |
| 0.0.59 | 12 / 8 | |
| 0.0.57 | 11 / 8 | |
| 0.0.56 | 11 / 8 | |
| 0.0.55 | 11 / 8 | |
| 0.0.54 | 11 / 8 | |
| 0.0.53 | 11 / 8 | |
| 0.0.52 | 11 / 8 | |
| 0.0.51 | 11 / 8 | |
| 0.0.50 | 11 / 8 | |
| 0.0.49 | 11 / 8 | |
| 0.0.48 | 11 / 8 | |
| 0.0.47 | 11 / 8 | |
| 0.0.46 | 11 / 8 | |
| 0.0.45 | 11 / 8 | |
| 0.0.44 | 11 / 8 | |
| 0.0.42 | 11 / 8 | |
| 0.0.41 | 11 / 8 |
v0.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
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-11, 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.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.