@meshsdk/core-cst
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): tsup --minify build output, consistent with build:mesh script; not true obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with sparse metadata; publisher has long track record, not spam. | ai | |
| phantom-deps | phantom-dep:blakejs | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:hash.js | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:base32-encoding | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:@harmoniclabs/pair | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:@harmoniclabs/uplc | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:@types/base32-encoding | AI (phantom-deps): TypeScript types package; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@harmoniclabs/plutus-data | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:@cardano-sdk/input-selection | AI (phantom-deps): Direct dep; used via @cardano-sdk/core re-exports. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| phantom-deps | phantom-dep:bech32 | AI (phantom-deps): Transitive dep from @cardano-sdk packages; correctly declared. | ai | |
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Base64-embedded WASM blake2b binary in bundled build, not hidden payload. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Base64-embedded WASM blake2b binary in bundled build, not hidden payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth from bundling new crypto deps (WASM), not injected payload. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer list churn in an active monorepo package. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 15 / 7 | |
| 1.9.0 | 15 / 7 | |
| 1.8.14 | 13 / 7 | |
| 1.8.13 | 13 / 7 | |
| 1.8.12 | 13 / 7 | |
| 1.8.11 | 13 / 7 | |
| 1.8.10 | 13 / 7 | |
| 1.8.9 | 13 / 7 | |
| 1.8.8 | 13 / 7 | |
| 1.8.7 | 13 / 7 | |
| 1.8.6 | 13 / 7 | |
| 1.8.5 | 13 / 7 | |
| 1.8.4 | 10 / 7 | |
| 1.8.3 | 10 / 7 | |
| 1.8.2 | 10 / 7 | |
| 1.8.1 | 10 / 7 | |
| 1.8.0 | 10 / 7 | |
| 1.7.33 | 10 / 7 | |
| 1.7.32 | 10 / 7 | |
| 1.7.31 | 10 / 7 | |
| 1.7.30 | 10 / 7 | |
| 1.7.29 | 10 / 7 | |
| 1.7.28 | 10 / 7 | |
| 1.7.27 | 10 / 7 | |
| 1.7.26 | 10 / 7 | |
| 1.7.25 | 10 / 7 | |
| 1.7.24 | 10 / 7 | |
| 1.7.23 | 10 / 7 | |
| 1.7.22 | 10 / 7 | |
| 1.7.21 | 10 / 7 | |
| 1.7.20 | 10 / 7 | |
| 1.7.19 | 10 / 7 | |
| 1.7.18 | 10 / 7 | |
| 1.7.17 | 10 / 7 | |
| 1.7.16 | 10 / 7 | |
| 1.7.15 | 10 / 7 | |
| 1.7.14 | 10 / 7 | |
| 1.7.13 | 10 / 7 | |
| 1.7.12 | 10 / 7 | |
| 1.7.11 | 10 / 7 | |
| 1.7.10 | 10 / 7 | |
| 1.7.9 | 10 / 7 | |
| 1.7.8 | 10 / 7 | |
| 1.7.7 | 10 / 7 | |
| 1.7.6 | 10 / 7 | |
| 1.7.5 | 10 / 7 | |
| 1.7.4 | 10 / 7 | |
| 1.7.3 | 10 / 7 | |
| 1.7.2 | 10 / 7 | |
| 1.7.1 | 10 / 7 | |
| 1.7.0 | 10 / 7 | |
| 1.6.13 | 10 / 7 | |
| 1.6.12 | 10 / 7 | |
| 1.6.11 | 10 / 7 | |
| 1.6.10 | 10 / 7 | |
| 1.6.9 | 10 / 7 | |
| 1.6.8 | 10 / 7 | |
| 1.6.7 | 10 / 7 | |
| 1.6.6 | 10 / 7 | |
| 1.6.5 | 11 / 7 | |
| 1.6.4 | 8 / 7 | |
| 1.6.3 | 8 / 7 | |
| 1.6.2 | 7 / 7 | |
| 1.6.1 | 7 / 7 | |
| 1.5.32 | 7 / 7 | |
| 1.5.30 | 7 / 7 | |
| 1.5.29 | 7 / 7 | |
| 1.5.28 | 7 / 7 |
v1.9.1
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 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.
This version was published by a different npm account (jinglescode) than the most recent previously approved version (sidan-lab) on 2026-06-19, but jinglescode is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
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.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
2 findingsNewly 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.
v1.6.1
2 findingsNewly 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.
v1.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.30
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 (sidan-lab) than the most recent previously approved version (jinglescode) on 2024-07-31, but sidan-lab is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.