@trezor/type-utils
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known trezor-ci maintainer publish; no material change, benign for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal type-utils lib; missing description is stable and benign. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo internal utility package; sparse metadata is normal for @trezor/* sub-packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 1 | |
| 1.1.9 | 0 / 1 | |
| 1.1.8 | 0 / 1 | |
| 1.1.7 | 0 / 1 | |
| 1.1.6 | 0 / 1 | |
| 1.1.5 | 0 / 0 | |
| 1.1.4 | 0 / 0 | |
| 1.1.3 | 0 / 0 | |
| 1.1.2 | 0 / 0 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.5 | 0 / 0 | |
| 1.0.4 | 0 / 2 | |
| 1.0.2 | 0 / 2 | |
| 1.0.0 | 0 / 2 |
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
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 (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2024-02-09, but trezor-ci 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.0.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: trezor-ci.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (trezor-ci) than the most recent previously approved version (martin_varmuza) on 2023-05-16, but trezor-ci 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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.