@swissquote/crafty-commons-swc
This package is NOT meant to be used outside Crafty.
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on require(packageJsonPath) used to read package.json metadata — not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dep of SWC compilation output; not directly imported by source. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.30.1 | 5 / 2 | |
| 1.30.0 | 5 / 2 | |
| 1.29.0 | 5 / 2 | |
| 1.28.1 | 5 / 2 | |
| 1.28.0 | 5 / 2 | |
| 1.27.0 | 5 / 2 | |
| 1.26.0 | 5 / 2 | |
| 1.25.0 | 5 / 2 | |
| 1.24.0 | 5 / 2 | |
| 1.23.0 | 5 / 2 | |
| 1.22.3 | 5 / 2 | |
| 1.22.2 | 5 / 2 | |
| 1.22.1 | 5 / 2 | |
| 1.22.0 | 4 / 2 |
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.