← Home

@teambit/cache

npm Repository Homepage
51
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

teambit-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007

Keywords

bitbit-aspectbit-core-aspectcomponentscollaborationweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Adds first-party @teambit sibling package, normal for this monorepo. ai
maintainer-change maintainer-removed AI (maintainer-change): Teambit org package with strong publisher track record; maintainer cleanup is routine for this project. ai
dependencies unvetted-dep:@teambit/harmony AI (dependencies): Internal @teambit ecosystem dependency; stable pattern across all @teambit/* packages. ai
dependencies unvetted-dep:@teambit/legacy.constants AI (dependencies): Internal @teambit ecosystem dependency; stable pattern across all @teambit/* packages. ai
npm-metadata no-description AI (npm-metadata): Teambit monorepo component packages consistently omit descriptions; stable pattern across all versions. ai
provenance no-provenance AI (provenance): Teambit publishes without Sigstore provenance; consistent across all 1609 versions. ai

Versions (showing 51 of 220)

View all versions
Version Deps Published
0.0.1420 5 / 5
0.0.1419 5 / 5
0.0.1418 5 / 5
0.0.1417 5 / 5
0.0.1416 5 / 5
0.0.1414 5 / 5
0.0.1413 5 / 5
0.0.1411 5 / 5
0.0.1410 5 / 5
0.0.1402 5 / 5
0.0.1400 5 / 5
0.0.1378 5 / 5
0.0.1377 5 / 5
0.0.1318 5 / 5
0.0.1317 5 / 5
0.0.1291 5 / 5
0.0.1288 5 / 5
0.0.1287 5 / 5
0.0.1286 5 / 5
0.0.1285 5 / 5
0.0.1284 5 / 5
0.0.1282 5 / 5
0.0.1280 5 / 5
0.0.1272 5 / 5
0.0.1158 5 / 6
0.0.1157 4 / 6
0.0.1156 4 / 6
0.0.1155 4 / 6
0.0.1154 4 / 6
0.0.1153 4 / 6
0.0.1152 4 / 6
0.0.1151 4 / 6
0.0.1150 4 / 6
0.0.1149 4 / 6
0.0.1148 4 / 6
0.0.1147 4 / 6
0.0.1146 4 / 6
0.0.1145 4 / 6
0.0.1144 4 / 6
0.0.1143 4 / 6
0.0.1142 4 / 6
0.0.1141 4 / 6
0.0.1140 4 / 6
0.0.1139 4 / 6
0.0.1138 4 / 6
0.0.1137 4 / 6
0.0.1136 4 / 6
0.0.1135 4 / 6
0.0.1134 4 / 6
0.0.1133 4 / 6
0.0.1132 4 / 6

v0.0.1272

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidfirst → teambit-owner (on 2025-04-22, known maintainer) provenance

This version was published by a different npm account (teambit-owner) than the most recent previously approved version (davidfirst) on 2025-04-22, 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.1158

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidfirst → shohamgilad (on 2024-12-10, known maintainer) provenance

This version was published by a different npm account (shohamgilad) than the most recent previously approved version (davidfirst) on 2024-12-10, but shohamgilad 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.1157

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1156

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1155

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1154

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1153

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1152

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1151

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1150

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1149

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1148

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1147

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1146

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1145

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1144

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1143

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1142

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1141

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1140

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1139

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1138

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1137

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1136

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1135

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1134

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1133

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1132

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.