@teambit/tracker
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/toolbox.promise.map-pool | AI (dependencies): Same-org first-party monorepo dep, consistent with existing @teambit deps. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.concurrency | AI (dependencies): Same-org first-party monorepo dep, consistent with existing @teambit deps. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Reflects monorepo module split, no injected/obfuscated code found. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @teambit dep from same monorepo, benign pattern for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI releases across many packages simultaneously; rapid publish is normal for this publisher. | ai | |
| dependencies | unvetted-dep:array-difference | AI (dependencies): Legitimate utility dep in established teambit/bit monorepo package. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy-bit-id | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.logger | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:firstline | AI (dependencies): Legitimate utility dep in established teambit/bit monorepo package. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.analytics | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.node-modules-linker | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo component; missing description is a cosmetic issue, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes 2000+ versions without provenance; consistent pattern, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.bit-map | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/envs | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* dep; stable monorepo publishing pattern. | ai |
Versions (showing 17 of 117)
| Version | Deps | Published |
|---|---|---|
| 1.0.273 | 15 / 5 | |
| 1.0.272 | 15 / 5 | |
| 1.0.271 | 15 / 5 | |
| 1.0.270 | 15 / 5 | |
| 1.0.269 | 15 / 5 | |
| 1.0.268 | 15 / 5 | |
| 1.0.267 | 15 / 5 | |
| 1.0.266 | 15 / 5 | |
| 1.0.265 | 15 / 5 | |
| 1.0.264 | 15 / 5 | |
| 1.0.263 | 15 / 5 | |
| 1.0.262 | 15 / 5 | |
| 1.0.261 | 15 / 5 | |
| 1.0.260 | 15 / 5 | |
| 1.0.259 | 15 / 5 | |
| 1.0.258 | 15 / 5 | |
| 1.0.257 | 15 / 5 |
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
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 (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-02, but davidfirst 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.
v1.0.259
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 (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-01, but davidfirst 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.
v1.0.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.