@operato/font
User interface to select font and create font.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): heartyoh is the declared author with 599 approved packages; transition from nalshya113 appears legitimate. | ai | |
| dependencies | unvetted-dep:@operato/i18n | AI (dependencies): Same-org sibling package; stable pattern across all @operato/font versions. | ai | |
| dependencies | unvetted-dep:@operato/input | AI (dependencies): Same-org sibling package; stable pattern across all @operato/font versions. | ai | |
| dependencies | unvetted-dep:@operato/headroom | AI (dependencies): Same-org sibling package; stable pattern across all @operato/font versions. | ai | |
| dependencies | unvetted-dep:@operato/pull-to-refresh | AI (dependencies): Same-org sibling package; stable pattern across all @operato/font versions. | ai | |
| provenance | no-provenance | AI (provenance): Established @operato org package; no provenance is consistent across all versions. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @operato/font is not a typosquat of 'got'; Levenshtein match is spurious for scoped packages. | ai | |
| phantom-deps | phantom-dep:@operato/utils | AI (phantom-deps): Same-org sibling dep; may be used transitively or in non-analyzed files. | ai | |
| phantom-deps | phantom-dep:@operato/headroom | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for this package. | ai | |
| phantom-deps | phantom-dep:@operato/attachment | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 9.2.25 | 11 / 19 | |
| 9.2.22 | 11 / 19 | |
| 9.2.21 | 11 / 19 | |
| 9.2.20 | 11 / 19 | |
| 9.2.19 | 11 / 19 | |
| 9.2.18 | 11 / 19 | |
| 9.2.16 | 11 / 19 | |
| 9.2.15 | 11 / 19 | |
| 9.2.14 | 11 / 19 | |
| 9.2.13 | 11 / 19 | |
| 9.2.12 | 11 / 19 | |
| 9.2.7 | 11 / 19 | |
| 9.2.6 | 11 / 19 | |
| 9.2.5 | 11 / 19 | |
| 9.2.1 | 11 / 19 | |
| 9.2.0 | 11 / 19 | |
| 8.2.24 | 11 / 19 | |
| 8.2.23 | 11 / 19 | |
| 8.2.22 | 11 / 19 | |
| 8.2.20 | 11 / 19 | |
| 8.2.19 | 11 / 19 | |
| 8.2.18 | 11 / 19 | |
| 8.2.17 | 11 / 19 | |
| 8.2.16 | 11 / 19 | |
| 8.2.15 | 11 / 19 | |
| 8.2.14 | 11 / 19 | |
| 8.2.13 | 11 / 19 |
v9.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.