@teambit/express
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): Internal @teambit sibling dependency, consistent with monorepo pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation within the teambit org; stable pattern across many versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.logger | AI (dependencies): Internal teambit scoped dependency; consistent with the package's ecosystem and publisher history. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established teambit component package; missing description is a consistent pattern across the family, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Teambit packages consistently lack provenance attestation; stable false positive for this publisher. | ai |
Versions (showing 51 of 233)
| Version | Deps | Published |
|---|---|---|
| 0.0.1450 | 7 / 4 | |
| 0.0.1448 | 7 / 4 | |
| 0.0.1426 | 7 / 4 | |
| 0.0.1425 | 7 / 4 | |
| 0.0.1424 | 7 / 4 | |
| 0.0.1423 | 7 / 4 | |
| 0.0.1422 | 7 / 4 | |
| 0.0.1420 | 7 / 4 | |
| 0.0.1419 | 7 / 4 | |
| 0.0.1416 | 7 / 4 | |
| 0.0.1415 | 7 / 4 | |
| 0.0.1414 | 7 / 4 | |
| 0.0.1413 | 7 / 4 | |
| 0.0.1412 | 7 / 4 | |
| 0.0.1410 | 7 / 4 | |
| 0.0.1409 | 7 / 4 | |
| 0.0.1408 | 7 / 4 | |
| 0.0.1406 | 7 / 4 | |
| 0.0.1383 | 7 / 4 | |
| 0.0.1364 | 7 / 4 | |
| 0.0.1295 | 7 / 4 | |
| 0.0.1293 | 7 / 4 | |
| 0.0.1292 | 7 / 4 | |
| 0.0.1290 | 7 / 4 | |
| 0.0.1288 | 7 / 4 | |
| 0.0.1286 | 7 / 4 | |
| 0.0.1201 | 7 / 4 | |
| 0.0.1200 | 7 / 4 | |
| 0.0.1198 | 7 / 4 | |
| 0.0.1193 | 7 / 4 | |
| 0.0.1188 | 7 / 4 | |
| 0.0.1186 | 7 / 4 | |
| 0.0.1185 | 7 / 4 | |
| 0.0.1181 | 7 / 4 | |
| 0.0.1180 | 7 / 4 | |
| 0.0.1175 | 7 / 4 | |
| 0.0.1173 | 7 / 4 | |
| 0.0.1165 | 7 / 4 | |
| 0.0.1163 | 6 / 4 | |
| 0.0.1162 | 6 / 4 | |
| 0.0.1161 | 6 / 4 | |
| 0.0.1160 | 6 / 4 | |
| 0.0.1159 | 6 / 4 | |
| 0.0.1158 | 6 / 4 | |
| 0.0.1157 | 6 / 4 | |
| 0.0.1156 | 6 / 4 | |
| 0.0.1155 | 6 / 4 | |
| 0.0.1154 | 6 / 4 | |
| 0.0.1153 | 6 / 4 | |
| 0.0.1152 | 6 / 4 | |
| 0.0.1151 | 6 / 4 |
v0.0.1450
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1448
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1201
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1200
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1198
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1193
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1188
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1186
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1185
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1181
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1180
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1175
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1173
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1165
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1159
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1158
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1157
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1154
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1153
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1152
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1151
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.