@novasamatech/host-papp
Polkadot app integration
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@scure/sr25519 | AI (phantom-deps): @scure/sr25519 is a declared dep used via config/type references in this crypto package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@novasamatech/host-api | AI (phantom-deps): Same-org peer dep declared in package.json; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established novasamatech/paritytech publisher; no provenance is common for this ecosystem. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.8.6 | 15 / 0 | |
| 0.8.5 | 15 / 0 | |
| 0.8.4 | 15 / 0 | |
| 0.8.3 | 15 / 0 | |
| 0.8.2 | 15 / 0 | |
| 0.8.1 | 15 / 0 | |
| 0.8.0 | 15 / 0 | |
| 0.7.9 | 13 / 0 | |
| 0.7.8 | 14 / 0 | |
| 0.7.7 | 14 / 0 | |
| 0.7.6 | 14 / 0 | |
| 0.6.17 | 17 / 0 | |
| 0.6.15 | 17 / 0 | |
| 0.6.14 | 17 / 0 | |
| 0.6.12 | 17 / 0 | |
| 0.6.10 | 17 / 0 | |
| 0.6.1 | 17 / 0 | |
| 0.5.2 | 15 / 0 | |
| 0.5.1 | 15 / 0 | |
| 0.5.0 | 15 / 0 |
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.