@teambit/api-reference.renderers.schema-node-member-summary
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 monorepo components routinely omit descriptions; not a malware indicator for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Teambit packages consistently lack provenance attestation; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill implicit dependency; stable false positive for this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.0.80 | 12 / 9 | |
| 0.0.79 | 12 / 9 | |
| 0.0.78 | 12 / 9 | |
| 0.0.77 | 12 / 9 | |
| 0.0.75 | 12 / 9 | |
| 0.0.74 | 12 / 9 | |
| 0.0.71 | 12 / 9 | |
| 0.0.70 | 12 / 9 | |
| 0.0.69 | 12 / 9 | |
| 0.0.68 | 12 / 9 | |
| 0.0.67 | 12 / 9 | |
| 0.0.66 | 12 / 9 | |
| 0.0.65 | 12 / 9 | |
| 0.0.64 | 12 / 9 | |
| 0.0.62 | 12 / 9 | |
| 0.0.60 | 12 / 9 | |
| 0.0.59 | 12 / 9 | |
| 0.0.58 | 12 / 9 | |
| 0.0.57 | 12 / 9 | |
| 0.0.56 | 11 / 9 | |
| 0.0.55 | 11 / 9 | |
| 0.0.54 | 11 / 9 | |
| 0.0.53 | 11 / 9 | |
| 0.0.52 | 11 / 9 | |
| 0.0.51 | 11 / 9 | |
| 0.0.50 | 11 / 9 | |
| 0.0.49 | 11 / 9 | |
| 0.0.48 | 11 / 9 | |
| 0.0.47 | 11 / 9 | |
| 0.0.46 | 11 / 9 | |
| 0.0.45 | 11 / 9 | |
| 0.0.44 | 11 / 9 | |
| 0.0.43 | 11 / 9 |
v0.0.64
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-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.62
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-15, 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.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.