@teambit/ci
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@teambit/legacy.consumer-component | AI (phantom-deps): Same-org @teambit scope; declared dep, likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@teambit/lane-id | AI (phantom-deps): Same-org @teambit scope; declared dep, likely used transitively or via re-export pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @teambit packages from the same org; low risk for this publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): teambit-owner has 882 approved packages; maintainer rotation within the org is expected. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 1519 versions; missing description is metadata gap, not malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is infrastructure choice; not a security disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@teambit/toolbox.string.random | AI (dependencies): First-party @teambit sibling dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): First-party @teambit sibling dep from the teambit/bit monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): First-party @teambit sibling dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): First-party @teambit sibling dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.modules.merge-helper | AI (dependencies): First-party @teambit sibling dep; stable pattern. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @teambit package; Levenshtein match against 'pg' is a false positive. | ai | |
| phantom-deps | phantom-dep:@teambit/objects | AI (phantom-deps): Same-org monorepo dep; may be used transitively or in dist files not scanned. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @teambit package; Levenshtein match against 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @teambit package; Levenshtein match against 'qs' is a false positive. | ai |
Versions (showing 9 of 109)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 15 / 2 | |
| 1.0.7 | 15 / 2 | |
| 1.0.6 | 15 / 2 | |
| 1.0.5 | 15 / 2 | |
| 1.0.4 | 15 / 2 | |
| 1.0.3 | 15 / 2 | |
| 1.0.2 | 15 / 2 | |
| 1.0.1 | 15 / 2 | |
| 1.0.0 | 15 / 2 |
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.