@jspm/core
This package contains the core libraries used in jspm 2.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in nodelibs/crypto.js is standard AES cipher implementation (parsing ciphertext from base64) in the crypto-browserify shim — not malicious payload hiding. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in nodelibs/crypto.js is standard AES cipher implementation (parsing IV from hex) in the crypto-browserify shim — not malicious payload hiding. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @jspm/core is a legitimate scoped package under the @jspm org; name similarity to 'cors' is purely coincidental and not a typosquat. | ai | |
| source-diff | encoded-string-file:nodelibs/crypto.js | AI (source-diff): @jspm/core ships minified/bundled ESM polyfills built via jspm build; long strings in nodelibs/*.js are minified bundle artifacts, not obfuscated payloads. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established JSPM core polyfill package; no deps by design (all bundled), no repo URL in package.json is a known gap but package has 37 versions and a trusted maintainer. | ai | |
| source-diff | net-exec-file:nodelibs/browser/assert.js | AI (source-diff): Browser polyfill bundles legitimately contain both network APIs and dynamic code execution patterns (vm/eval polyfills); not malware indicators for this package. | ai | |
| source-diff | obfuscated-file:nodelibs/browser/assert.js | AI (source-diff): Files in nodelibs/browser/ are rollup-bundled polyfills for Node.js built-ins; minified output is expected and intentional for this package. | ai | |
| source-diff | net-exec-file:nodelibs/browser/chunk-CjPlbOtt.js | AI (source-diff): Browser polyfill chunk (Object.assign shim). Network+exec pattern is a false positive for bundled browser shims in this package. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): vm-browserify uses eval() by design to implement Node's vm.Script.runInThisContext(). This is the expected behavior of a vm module shim. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): timers-browserify shim uses new Function() to replicate Node's setTimeout string-callback behavior. Legitimate and documented upstream. | ai | |
| source-diff | encoded-string-file:nodelibs/browser/crypto.js | AI (source-diff): crypto.js is a bundled crypto-browserify output; long encoded strings are crypto constants. vm-browserify's iframe+eval is documented behavior for the vm shim. | ai | |
| source-diff | net-exec-file:nodelibs/browser/chunk-DtcTpLWz.js | AI (source-diff): Browser polyfill chunk (hasSymbols detection). Network+exec pattern is a false positive for bundled browser shims in this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 30 | |
| 2.0.1 | 0 / 30 | |
| 2.0.0 | 0 / 30 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.4 | 0 / 0 | |
| 1.0.3 | 0 / 0 | |
| 1.0.2 | 0 / 26 | |
| 1.0.1 | 0 / 27 | |
| 1.0.0 | 0 / 27 |
v2.1.0
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Modified file contains 28 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: guybedford.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: guybedford.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage name '@jspm/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.