@ts-for-gir/generator-html-doc
HTML Documentation generator for ts-for-gir
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ts-for-gir/lib | AI (dependencies): First-party sibling package in the same @ts-for-gir monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ts-for-gir/typedoc-theme | AI (dependencies): First-party sibling package in the same @ts-for-gir monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ts-for-gir/generator-base | AI (dependencies): First-party sibling package in the same @ts-for-gir monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@ts-for-gir/generator-json | AI (dependencies): First-party sibling package in the same @ts-for-gir monorepo; not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@ts-for-gir/generator-base | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive for monorepo packages. | ai |
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.