@ts-for-gir/cli
TypeScript type definition generator for GObject introspection GIR files
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @ts-for-gir/cli; Levenshtein match to 'joi' is purely coincidental, no impersonation intent. | ai | |
| phantom-deps | phantom-dep:ejs | AI (phantom-deps): ejs is a legitimate runtime dep used for template rendering; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:typedoc | AI (phantom-deps): typedoc used as a runtime dep for doc generation; indirect usage is expected for this tool. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): inquirer is a declared runtime dep; indirect import pattern is stable for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ts-for-gir/templates | AI (phantom-deps): Same-org scoped package; indirect usage via template processing scripts is expected. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.4 | 9 / 15 | |
| 4.0.3 | 9 / 16 | |
| 4.0.2 | 9 / 16 | |
| 4.0.1 | 9 / 16 | |
| 4.0.0 | 9 / 16 |
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.