typedoc
Create api documentation for TypeScript projects.
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Large file count reflects legitimate major version expansion with new locale/theme build outputs. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are established packages replacing prior equivalents; consistent with documented major version changes. | ai | |
| dependencies | unvetted-dep:marked | AI (dependencies): marked is a mainstream Markdown parser; its use in a documentation generator like typedoc is expected and benign. No advisories affect this version range. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of comparing against v0.25.0 as baseline. TypeDoc is actively maintained; the gap reflects registry data limitations, not actual inactivity. | ai | |
| provenance | publisher-changed | AI (provenance): TypeStrong/TypeDoc migrated publishing to GitHub Actions CI/CD with SLSA provenance attestation. This is a legitimate infrastructure change for a well-known package. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation provides stronger commit linkage than gitHead. Missing gitHead is expected when publishing via GitHub Actions with Sigstore. | ai | |
| provenance | no-provenance | AI (provenance): TypeDoc is a well-established documentation generator; lack of provenance is common and not a risk signal for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known Markdown parser; its use in a documentation generator is expected and legitimate. | ai | |
| dependencies | unvetted-dep:@gerrit0/mini-shiki | AI (dependencies): @gerrit0/mini-shiki is a syntax highlighter maintained by the TypeDoc author; its use in a documentation generator is expected and legitimate. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.28.18 | 5 / 16 | |
| 0.28.12 | 5 / 16 | |
| 0.25.10 | 4 / 15 | |
| 0.25.0 | 4 / 15 |
v0.28.18
3 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.28.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: typedoc-bot.
v0.25.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.