@pmndrs/uikit
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @zappar/msdf-generator is a legitimate MSDF font tool consistent with uikit's text rendering functionality. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD is a legitimate automation pattern; SLSA attestation confirms integrity. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer added to an established org package; consistent with normal team growth in the pmndrs org. | ai | |
| dependencies | unvetted-dep:@pmndrs/msdfonts | AI (dependencies): Same pmndrs org sibling package; consistent with uikit's font rendering functionality. | ai | |
| dependencies | unvetted-dep:@pmndrs/uikit-pub-sub | AI (dependencies): Same pmndrs org sibling package; consistent with uikit's pub-sub architecture. | ai | |
| dependencies | unvetted-dep:@zappar/msdf-generator | AI (dependencies): Known MSDF font generation library used for 3D text rendering; expected dependency for this package. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 1.0.73 | 6 / 0 | |
| 1.0.72 | 6 / 0 | |
| 1.0.71 | 6 / 0 | |
| 1.0.70 | 6 / 0 | |
| 1.0.69 | 6 / 0 | |
| 1.0.68 | 5 / 0 | |
| 1.0.67 | 5 / 0 | |
| 1.0.66 | 5 / 0 | |
| 1.0.64 | 5 / 0 | |
| 1.0.63 | 5 / 0 | |
| 1.0.62 | 5 / 0 | |
| 1.0.61 | 5 / 0 | |
| 1.0.60 | 4 / 0 | |
| 1.0.59 | 4 / 0 | |
| 1.0.58 | 4 / 0 | |
| 1.0.57 | 4 / 0 | |
| 1.0.56 | 4 / 0 | |
| 1.0.55 | 4 / 0 | |
| 1.0.54 | 4 / 0 | |
| 1.0.53 | 4 / 0 | |
| 1.0.52 | 4 / 0 | |
| 1.0.51 | 4 / 0 | |
| 1.0.50 | 4 / 0 | |
| 1.0.49 | 4 / 0 | |
| 1.0.48 | 4 / 0 | |
| 1.0.47 | 7 / 0 | |
| 1.0.46 | 7 / 0 | |
| 1.0.45 | 7 / 0 | |
| 1.0.44 | 7 / 0 | |
| 1.0.43 | 7 / 0 | |
| 1.0.42 | 7 / 0 | |
| 1.0.41 | 7 / 0 | |
| 1.0.40 | 7 / 0 | |
| 1.0.38 | 7 / 0 | |
| 1.0.37 | 7 / 0 | |
| 1.0.36 | 7 / 0 | |
| 1.0.35 | 7 / 0 | |
| 1.0.34 | 7 / 0 | |
| 1.0.33 | 7 / 0 | |
| 1.0.32 | 7 / 0 | |
| 1.0.31 | 7 / 0 | |
| 1.0.30 | 7 / 0 | |
| 1.0.29 | 7 / 0 | |
| 1.0.28 | 7 / 0 | |
| 1.0.27 | 7 / 0 | |
| 1.0.26 | 7 / 0 | |
| 1.0.25 | 7 / 0 | |
| 1.0.24 | 7 / 0 | |
| 1.0.23 | 7 / 0 | |
| 1.0.22 | 7 / 0 | |
| 1.0.21 | 7 / 0 | |
| 1.0.20 | 7 / 0 | |
| 1.0.19 | 7 / 0 | |
| 1.0.18 | 7 / 0 | |
| 1.0.17 | 7 / 0 | |
| 1.0.16 | 7 / 0 | |
| 1.0.15 | 7 / 0 | |
| 1.0.14 | 7 / 0 | |
| 1.0.13 | 7 / 0 | |
| 1.0.12 | 7 / 0 | |
| 1.0.11 | 7 / 0 | |
| 1.0.10 | 7 / 0 | |
| 1.0.9 | 7 / 0 | |
| 1.0.8 | 7 / 0 | |
| 1.0.7 | 7 / 0 | |
| 1.0.6 | 7 / 0 | |
| 1.0.5 | 7 / 0 | |
| 1.0.4 | 7 / 0 | |
| 1.0.3 | 7 / 0 | |
| 1.0.2 | 7 / 0 | |
| 1.0.1 | 7 / 0 | |
| 1.0.0 | 7 / 0 |
v1.0.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.63
2 findingsThis version was published by a different npm account than previous versions on 2026-03-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.62
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.61
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.