@pmate/cli
CLI utilities for the pMate project
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish workflow change (prepare script removed) plausibly explains missing gitHead; no other risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @pmate/cli versions; low-risk internal tooling package. | ai | |
| phantom-deps | phantom-dep:@pmate/chat-sdk | AI (phantom-deps): Same-org package; likely used transitively or bundled rather than directly imported. | ai | |
| dependencies | unvetted-dep:@alicloud/openapi-client | AI (dependencies): Official Alibaba Cloud OpenAPI client; foundational dependency for Alibaba Cloud SDKs used in this package. | ai | |
| dependencies | unvetted-dep:@alicloud/alidns20150109 | AI (dependencies): Official Alibaba Cloud DNS SDK; expected for a CLI managing Alibaba Cloud resources. | ai | |
| dependencies | unvetted-dep:jsqr | AI (dependencies): jsqr is a well-known, legitimate QR code reading library; expected dependency for a CLI tool with QR functionality. | ai | |
| dependencies | unvetted-dep:@alicloud/cdn20180510 | AI (dependencies): Official Alibaba Cloud CDN SDK; expected for a CLI managing Alibaba Cloud resources. | ai | |
| phantom-deps | phantom-dep:@pmate/meta | AI (phantom-deps): Same-org scoped package; declared as a dependency in a monorepo-style project. Not being directly imported is expected for shared metadata/type packages. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @pmate/cli is a scoped CLI tool for the pMate project; the levenshtein match to 'joi' is purely coincidental with no impersonation intent. | ai | |
| phantom-deps | phantom-dep:@types/ali-oss | AI (phantom-deps): @types/ali-oss is a type declaration package loaded by convention; not being directly imported is expected behavior. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declaring it as a dependency for downstream consumers is a common and legitimate pattern. | ai |
Versions (showing 100 of 149)
| Version | Deps | Published |
|---|---|---|
| 0.24.31 | 20 / 10 | |
| 0.24.30 | 20 / 10 | |
| 0.24.29 | 20 / 10 | |
| 0.24.28 | 20 / 10 | |
| 0.24.27 | 20 / 10 | |
| 0.24.26 | 20 / 10 | |
| 0.24.25 | 20 / 10 | |
| 0.24.24 | 20 / 10 | |
| 0.24.23 | 20 / 10 | |
| 0.24.22 | 20 / 10 | |
| 0.24.21 | 20 / 10 | |
| 0.24.20 | 20 / 10 | |
| 0.24.19 | 20 / 10 | |
| 0.24.18 | 20 / 10 | |
| 0.24.17 | 20 / 10 | |
| 0.24.16 | 20 / 10 | |
| 0.24.15 | 20 / 10 | |
| 0.24.14 | 20 / 10 | |
| 0.24.13 | 20 / 10 | |
| 0.24.12 | 20 / 10 | |
| 0.24.11 | 20 / 10 | |
| 0.24.10 | 20 / 10 | |
| 0.24.9 | 19 / 10 | |
| 0.24.8 | 19 / 10 | |
| 0.24.7 | 19 / 10 | |
| 0.24.6 | 19 / 10 | |
| 0.24.5 | 19 / 9 | |
| 0.24.4 | 19 / 9 | |
| 0.24.3 | 19 / 9 | |
| 0.24.2 | 19 / 9 | |
| 0.24.1 | 17 / 9 | |
| 0.24.0 | 17 / 9 | |
| 0.23.0 | 17 / 9 | |
| 0.22.0 | 17 / 9 | |
| 0.21.19 | 17 / 9 | |
| 0.21.18 | 17 / 9 | |
| 0.21.17 | 17 / 9 | |
| 0.21.16 | 17 / 9 | |
| 0.21.15 | 17 / 9 | |
| 0.21.14 | 17 / 9 | |
| 0.21.13 | 17 / 9 | |
| 0.21.12 | 17 / 9 | |
| 0.21.11 | 17 / 9 | |
| 0.21.10 | 17 / 9 | |
| 0.21.9 | 17 / 9 | |
| 0.21.8 | 16 / 9 | |
| 0.21.7 | 15 / 9 | |
| 0.21.6 | 15 / 9 | |
| 0.21.5 | 15 / 9 | |
| 0.21.4 | 15 / 9 | |
| 0.21.3 | 15 / 9 | |
| 0.21.2 | 15 / 9 | |
| 0.21.1 | 15 / 9 | |
| 0.21.0 | 15 / 9 | |
| 0.20.11 | 15 / 9 | |
| 0.20.10 | 15 / 9 | |
| 0.20.9 | 15 / 9 | |
| 0.20.8 | 15 / 9 | |
| 0.20.7 | 15 / 9 | |
| 0.20.6 | 15 / 9 | |
| 0.20.5 | 15 / 9 | |
| 0.20.4 | 15 / 9 | |
| 0.20.3 | 15 / 9 | |
| 0.20.2 | 15 / 9 | |
| 0.20.1 | 15 / 9 | |
| 0.20.0 | 15 / 9 | |
| 0.19.0 | 15 / 9 | |
| 0.18.0 | 15 / 9 | |
| 0.17.8 | 15 / 9 | |
| 0.17.7 | 15 / 9 | |
| 0.17.6 | 15 / 9 | |
| 0.17.5 | 15 / 9 | |
| 0.17.4 | 15 / 9 | |
| 0.17.3 | 15 / 9 | |
| 0.17.2 | 15 / 9 | |
| 0.17.1 | 15 / 9 | |
| 0.17.0 | 15 / 9 | |
| 0.16.4 | 15 / 9 | |
| 0.16.3 | 15 / 9 | |
| 0.16.2 | 15 / 9 | |
| 0.16.1 | 15 / 9 | |
| 0.16.0 | 15 / 9 | |
| 0.15.0 | 15 / 9 | |
| 0.14.0 | 15 / 9 | |
| 0.13.3 | 15 / 9 | |
| 0.13.2 | 15 / 9 | |
| 0.13.1 | 15 / 9 | |
| 0.13.0 | 15 / 9 | |
| 0.12.8 | 15 / 9 | |
| 0.12.7 | 17 / 6 | |
| 0.12.6 | 17 / 6 | |
| 0.12.4 | 17 / 6 | |
| 0.12.3 | 17 / 6 | |
| 0.11.2 | 15 / 6 | |
| 0.11.1 | 15 / 6 | |
| 0.11.0 | 15 / 6 | |
| 0.10.1 | 15 / 6 | |
| 0.10.0 | 15 / 6 | |
| 0.9.0 | 15 / 6 | |
| 0.8.12 | 15 / 5 |
v0.24.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.24
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ramroll.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.23
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ramroll.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.22
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ramroll.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ramroll.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ramroll.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ramroll.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.