@swissquote/crafty-preset-babel
<table> <tr><th>Compatible Runners</th><td>
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:babel-loader | AI (phantom-deps): Used as gulp/babel loader plugin, not imported directly; standard for build presets. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-specified config file path, core to preset's configurator function. | ai | |
| phantom-deps | phantom-dep:eslint-loader | AI (phantom-deps): Used as webpack/gulp loader plugin by config reference, not import. | ai | |
| source-diff | net-exec-file:dist/compiled/babel-packages.js | AI (source-diff): Webpack/ncc-bundled babel vendor code, not a dropper; consistent with build tool's compiled output. | ai | |
| source-diff | obfuscated-file:dist/compiled/sourcemap-register.js | AI (source-diff): Minified sourcemap-register vendor lib, standard bundler output not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): stephane.goetz is a known, email-matched maintainer with long track record on this package. | ai | |
| dependencies | unvetted-dep:gulp-eslint7 | AI (dependencies): Standard gulp-eslint successor package, used only as build tooling. | ai | |
| phantom-deps | phantom-dep:@babel/helper-module-imports | AI (phantom-deps): Babel helper loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel helper; loaded by convention, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@swissquote/crafty-commons-webpack | AI (phantom-deps): Same-org monorepo dep; loaded by plugin convention, not direct import. | ai | |
| phantom-deps | phantom-dep:schema-utils | AI (phantom-deps): Declared as runtime dep; loaded by convention via webpack config, not directly imported. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.30.2 | 9 / 3 | |
| 1.30.1 | 9 / 3 | |
| 1.30.0 | 9 / 3 | |
| 1.29.0 | 9 / 3 | |
| 1.28.1 | 9 / 3 | |
| 1.26.0 | 9 / 3 | |
| 1.19.1 | 8 / 4 | |
| 1.19.0 | 8 / 4 | |
| 1.18.2 | 9 / 4 | |
| 1.17.2 | 13 / 0 | |
| 1.17.1 | 13 / 0 | |
| 1.16.3 | 13 / 0 | |
| 1.16.1 | 13 / 0 | |
| 1.16.0 | 13 / 0 | |
| 1.15.0 | 15 / 0 | |
| 1.14.0 | 15 / 0 | |
| 1.13.7 | 15 / 0 | |
| 1.13.5 | 15 / 0 | |
| 1.13.4 | 15 / 0 | |
| 1.13.3 | 15 / 0 | |
| 1.13.2 | 15 / 0 | |
| 1.13.0 | 15 / 0 | |
| 1.12.0 | 14 / 0 | |
| 1.11.1 | 14 / 0 | |
| 1.11.0 | 14 / 0 | |
| 1.10.0 | 14 / 0 | |
| 1.9.1 | 14 / 0 | |
| 1.9.0 | 14 / 0 | |
| 1.8.0 | 14 / 0 | |
| 1.7.3 | 14 / 0 | |
| 1.7.2 | 14 / 0 | |
| 1.7.1 | 14 / 0 | |
| 1.7.0 | 14 / 0 | |
| 1.6.0 | 21 / 0 | |
| 1.5.0 | 22 / 0 | |
| 1.4.0 | 22 / 0 | |
| 1.3.0 | 23 / 0 | |
| 1.2.1 | 23 / 0 | |
| 1.2.0 | 23 / 0 | |
| 1.1.0 | 23 / 0 |
v1.30.2
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.19.1
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2022-04-25, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.19.0
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2022-04-21, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.18.2
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2022-02-23, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.17.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2021-11-01, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.17.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2021-10-29, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stephane.goetz) than the most recent previously approved version (onigoetz) on 2021-03-08, but stephane.goetz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.