@ton/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/tuple/tuple.spec.js | AI (source-diff): Base64url BOC test-vector fixtures in test files; benign and recurring. | ai | |
| source-diff | encoded-string-file:dist/types/MessageRelaxed.spec.js | AI (source-diff): Base64 BOC test fixtures in spec file; normal for TON serialization library. | ai | |
| source-diff | encoded-string-file:src/types/Transaction.spec.ts | AI (source-diff): Base64 BOC transaction fixtures in test files; stable for this package. | ai | |
| source-diff | encoded-string-file:dist/types/Transaction.spec.js | AI (source-diff): Base64 BOC transaction fixtures in test files; stable for this package. | ai | |
| source-diff | encoded-string-file:src/boc/cell/serialization.spec.ts | AI (source-diff): Hex BOC wallet test vectors in serialization spec; stable for this TON lib. | ai | |
| source-diff | encoded-string-file:dist/boc/cell/serialization.spec.js | AI (source-diff): Hex BOC wallet test vectors in serialization spec; stable for this TON lib. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @ton/core is a scoped TON blockchain SDK, not a typosquat of 'cors'. The Levenshtein comparison is a false positive; these packages have entirely different purposes and namespaces. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for parsing raw TON blockchain addresses — standard address parsing logic in a blockchain SDK, not obfuscation or malicious payload handling. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used for parsing ADNL blockchain addresses from their canonical string representation — standard, expected behavior for a blockchain SDK. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.63.1 | 0 / 10 | |
| 0.63.0 | 0 / 10 | |
| 0.62.1 | 0 / 10 | |
| 0.62.0 | 1 / 12 | |
| 0.61.0 | 1 / 12 | |
| 0.60.1 | 1 / 12 | |
| 0.60.0 | 1 / 12 | |
| 0.59.1 | 1 / 12 | |
| 0.59.0 | 1 / 12 | |
| 0.58.1 | 1 / 12 | |
| 0.58.0 | 1 / 12 | |
| 0.57.0 | 1 / 12 | |
| 0.56.3 | 1 / 12 | |
| 0.56.2 | 1 / 12 | |
| 0.56.1 | 1 / 12 | |
| 0.56.0 | 1 / 12 | |
| 0.55.0 | 1 / 12 | |
| 0.54.0 | 1 / 12 | |
| 0.53.0 | 1 / 12 | |
| 0.52.2 | 1 / 12 | |
| 0.52.1 | 1 / 12 | |
| 0.52.0 | 1 / 12 | |
| 0.51.0 | 1 / 12 | |
| 0.49.2 | 1 / 12 | |
| 0.49.1 | 1 / 12 |
v0.60.1
3 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 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.
v0.60.0
3 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 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.
v0.59.1
3 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 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.
v0.59.0
3 findingsModified file contains 5 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 5 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.
v0.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
2 findingsModified file contains 2 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.
v0.56.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 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.
v0.55.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 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.
v0.54.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 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.
v0.53.0
2 findingsModified file contains 4 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.
v0.52.2
3 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 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.
v0.52.1
3 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 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.
v0.52.0
4 findingsModified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (mrmld) than the most recent previously approved version (ikardanov) on 2023-08-24. It has since remained available on npm for 1061 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
2 findingsThis version was published by a different npm account (mrmld) than the most recent previously approved version (ikardanov) on 2023-08-22. It has since remained available on npm for 1064 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.