@teambit/ripple
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @teambit/export is a first-party teambit package; addition is consistent with the package's scope and publisher track record. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI/CD publishing across hundreds of packages; rapid publish is a stable pattern for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component; description often omitted for internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo; provenance adoption is org-wide, not per-package risk. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org, not an independent risk. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org. | ai | |
| dependencies | unvetted-dep:@teambit/cloud | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org. | ai | |
| dependencies | unvetted-dep:@teambit/export | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Sibling @teambit monorepo dependency; same publisher org. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.0.87 | 10 / 2 | |
| 0.0.86 | 10 / 2 | |
| 0.0.84 | 10 / 2 | |
| 0.0.79 | 10 / 2 | |
| 0.0.77 | 10 / 2 | |
| 0.0.76 | 10 / 2 | |
| 0.0.75 | 10 / 2 | |
| 0.0.74 | 10 / 2 | |
| 0.0.72 | 10 / 2 | |
| 0.0.71 | 10 / 2 | |
| 0.0.70 | 10 / 2 | |
| 0.0.69 | 10 / 2 | |
| 0.0.68 | 10 / 2 | |
| 0.0.67 | 10 / 2 | |
| 0.0.66 | 10 / 2 | |
| 0.0.65 | 10 / 2 | |
| 0.0.64 | 10 / 2 | |
| 0.0.63 | 10 / 2 | |
| 0.0.62 | 10 / 2 | |
| 0.0.61 | 10 / 2 | |
| 0.0.60 | 10 / 2 | |
| 0.0.59 | 10 / 2 | |
| 0.0.58 | 10 / 2 | |
| 0.0.57 | 10 / 2 | |
| 0.0.56 | 10 / 2 | |
| 0.0.55 | 10 / 2 | |
| 0.0.54 | 10 / 2 | |
| 0.0.53 | 10 / 2 | |
| 0.0.51 | 10 / 2 | |
| 0.0.50 | 10 / 2 | |
| 0.0.49 | 10 / 2 | |
| 0.0.48 | 10 / 2 | |
| 0.0.47 | 10 / 2 | |
| 0.0.46 | 10 / 2 | |
| 0.0.45 | 10 / 2 | |
| 0.0.42 | 9 / 2 | |
| 0.0.35 | 9 / 2 | |
| 0.0.34 | 9 / 2 | |
| 0.0.28 | 9 / 2 | |
| 0.0.24 | 9 / 2 | |
| 0.0.19 | 9 / 2 | |
| 0.0.16 | 9 / 2 | |
| 0.0.14 | 9 / 2 | |
| 0.0.12 | 9 / 2 | |
| 0.0.5 | 9 / 2 | |
| 0.0.4 | 9 / 2 | |
| 0.0.2 | 9 / 2 | |
| 0.0.1 | 9 / 2 |
v0.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.