@polkadot/typegen
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a legitimate templating library used intentionally by this type-generation tool. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established polkadot-js ecosystem package; sparse README is a style choice, not a spam indicator. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 16.5.4 | 17 / 0 | |
| 16.5.3 | 17 / 0 | |
| 16.4.7 | 17 / 0 | |
| 16.4.4 | 17 / 0 | |
| 16.4.3 | 17 / 0 | |
| 16.4.2 | 17 / 0 | |
| 16.3.1 | 17 / 0 | |
| 16.2.2 | 17 / 0 | |
| 16.1.2 | 17 / 0 | |
| 16.1.1 | 17 / 0 |
v16.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.