@3-/lang
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@3-/camel | AI (phantom-deps): Same-org dep; phantom-dep heuristic fires on indirect/re-exported usage patterns common in this package family. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.2.15 | 0 / 9 | |
| 0.2.14 | 0 / 9 | |
| 0.2.13 | 0 / 9 | |
| 0.2.12 | 1 / 8 | |
| 0.2.11 | 1 / 8 | |
| 0.2.10 | 1 / 8 | |
| 0.2.9 | 1 / 8 | |
| 0.2.8 | 1 / 8 | |
| 0.2.7 | 1 / 8 | |
| 0.2.6 | 1 / 8 | |
| 0.2.5 | 1 / 8 | |
| 0.2.4 | 1 / 8 | |
| 0.2.2 | 1 / 8 | |
| 0.2.1 | 1 / 8 | |
| 0.1.22 | 0 / 8 | |
| 0.1.20 | 0 / 8 | |
| 0.1.19 | 2 / 8 | |
| 0.1.18 | 2 / 8 | |
| 0.1.16 | 2 / 8 | |
| 0.1.15 | 2 / 8 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.