@talismn/chaindata-provider
`initChaindata.json` file should never be edit manually. it needs to be regenerated before each release using `pnpm chore:generate-init-data`
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 | obfuscated-file:dist/index.d.ts | AI (source-diff): TypeScript declaration file with long lines from generated type signatures; not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation is a documented, legitimate supply-chain improvement for this org. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard tsup/esbuild bundle output; samples show readable library code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Standard tsup/esbuild ESM bundle; samples show readable library code. | ai | |
| source-diff | obfuscated-file:dist/index.d.mts | AI (source-diff): TypeScript declaration file with long lines from generated type signatures; not obfuscation. | ai | |
| source-diff | encoded-string-file:dist/talismn-chaindata-provider.cjs.dev.js | AI (source-diff): Long hex strings are Substrate SCALE-encoded chain metadata (miniMetadatas), not obfuscated payloads; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/talismn-chaindata-provider.cjs.prod.js | AI (source-diff): Same Substrate SCALE metadata pattern; benign for this package. | ai | |
| source-diff | encoded-string-file:dist/talismn-chaindata-provider.esm.js | AI (source-diff): Same Substrate SCALE metadata pattern; benign for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Talisman org package; sparse README/keywords are cosmetic, not indicative of spam. | ai | |
| dependencies | unvetted-dep:@talismn/util | AI (dependencies): Same-org sibling dependency from TalismanSociety; stable pattern across versions. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 7 / 4 | |
| 1.3.9 | 7 / 4 | |
| 1.3.8 | 7 / 4 | |
| 1.3.7 | 7 / 4 | |
| 1.3.6 | 7 / 4 | |
| 1.3.5 | 7 / 4 | |
| 1.3.4 | 7 / 10 | |
| 1.3.3 | 7 / 10 | |
| 1.3.2 | 7 / 10 | |
| 1.3.1 | 7 / 10 | |
| 1.3.0 | 7 / 10 | |
| 1.2.0 | 7 / 10 | |
| 1.1.6 | 7 / 10 | |
| 1.1.5 | 7 / 10 | |
| 1.1.4 | 7 / 10 | |
| 1.1.2 | 7 / 10 | |
| 1.1.1 | 7 / 10 | |
| 1.1.0 | 7 / 10 | |
| 1.0.2 | 6 / 10 | |
| 1.0.1 | 6 / 10 | |
| 1.0.0 | 6 / 10 |
v1.3.9
6 findingsThis version was published by a different npm account than previous versions on 2026-04-03. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.8
6 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.7
6 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
6 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.5
6 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.4
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.3.3
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.3.2
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.3.1
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.3.0
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.2.0
4 findingsModified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 16 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.6
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.5
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.4
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.2
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.1
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.2
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.1
4 findingsModified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 15 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.