@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 33 of 233)
| Version | Deps | Published |
|---|---|---|
| 0.0.994 | 6 / 5 | |
| 0.0.993 | 6 / 5 | |
| 0.0.992 | 6 / 5 | |
| 0.0.991 | 6 / 5 | |
| 0.0.990 | 6 / 5 | |
| 0.0.989 | 6 / 5 | |
| 0.0.988 | 6 / 5 | |
| 0.0.987 | 6 / 5 | |
| 0.0.986 | 6 / 5 | |
| 0.0.985 | 6 / 5 | |
| 0.0.984 | 6 / 5 | |
| 0.0.983 | 6 / 5 | |
| 0.0.982 | 6 / 5 | |
| 0.0.981 | 6 / 5 | |
| 0.0.980 | 6 / 5 | |
| 0.0.979 | 6 / 5 | |
| 0.0.978 | 6 / 5 | |
| 0.0.977 | 6 / 5 | |
| 0.0.976 | 6 / 5 | |
| 0.0.975 | 6 / 5 | |
| 0.0.974 | 6 / 5 | |
| 0.0.973 | 6 / 5 | |
| 0.0.972 | 6 / 5 | |
| 0.0.971 | 6 / 5 | |
| 0.0.970 | 6 / 5 | |
| 0.0.969 | 6 / 5 | |
| 0.0.968 | 6 / 5 | |
| 0.0.967 | 6 / 5 | |
| 0.0.966 | 6 / 5 | |
| 0.0.965 | 6 / 5 | |
| 0.0.964 | 6 / 5 | |
| 0.0.963 | 6 / 5 | |
| 0.0.962 | 6 / 5 |
v0.0.994
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.993
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.992
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.991
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.990
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.989
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.988
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.987
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.986
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.985
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.984
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.983
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.982
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.981
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.980
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.979
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.978
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.977
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.976
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.975
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.974
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.973
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.972
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.971
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.969
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.968
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.967
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.966
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.965
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.964
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.963
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.962
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.