@docusaurus/types
Common types for Docusaurus packages.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Monorepo package; maintainer rotation is expected and does not indicate takeover. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice recommendation; absence is not a security blocker for an established package from a trusted publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dependency is @types/mdast, a standard types package; no security risk. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing; not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Types-only package; README and keyword signals not material for type definitions. | ai | |
| dependencies | unvetted-dep:@types/history | AI (dependencies): Established types package; appropriate for a types-focused package. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped type package; declared but not directly imported is expected. | ai | |
| dependencies | unvetted-dep:@types/mdast | AI (dependencies): Standard type dependency for a types package; reasonable version constraint. | ai | |
| dependencies | unvetted-dep:webpack-merge | AI (dependencies): Build tool dependency with stable version constraint; appropriate for Docusaurus types package. | ai | |
| dependencies | unvetted-dep:joi | AI (dependencies): joi is an established validation library; appropriate for a types package's build dependencies. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): Framework-scoped type package; declared but not directly imported is expected. | ai | |
| dependencies | unvetted-dep:webpack | AI (dependencies): webpack is a standard build tool; expected in Docusaurus monorepo dependencies. | ai | |
| dependencies | unvetted-dep:react-helmet-async | AI (dependencies): react-helmet-async is a standard React utility; reasonable for Docusaurus types. | ai | |
| phantom-deps | phantom-dep:@types/history | AI (phantom-deps): Framework-scoped type package; declared but not directly imported is expected. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 10 / 0 | |
| 3.10.0 | 10 / 0 | |
| 3.9.2 | 10 / 0 | |
| 3.9.1 | 10 / 0 | |
| 3.9.0 | 10 / 0 | |
| 3.8.1 | 9 / 0 | |
| 3.8.0 | 9 / 0 | |
| 3.7.0 | 9 / 0 | |
| 3.6.3 | 9 / 0 | |
| 3.6.2 | 9 / 0 | |
| 3.6.1 | 9 / 0 | |
| 3.6.0 | 9 / 0 | |
| 3.5.2 | 9 / 0 | |
| 3.5.1 | 9 / 0 | |
| 3.5.0 | 9 / 0 | |
| 3.4.0 | 9 / 0 | |
| 3.3.2 | 9 / 0 | |
| 3.3.0 | 9 / 0 | |
| 3.2.1 | 9 / 0 | |
| 3.2.0 | 9 / 0 | |
| 3.1.1 | 9 / 0 | |
| 3.1.0 | 9 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 | |
| 2.4.3 | 8 / 0 | |
| 2.4.2 | 8 / 0 | |
| 2.4.1 | 8 / 0 | |
| 2.4.0 | 8 / 0 | |
| 2.3.1 | 8 / 0 | |
| 2.3.0 | 8 / 0 | |
| 2.2.0 | 8 / 0 | |
| 2.1.0 | 8 / 0 | |
| 2.0.1 | 8 / 0 | |
| 2.0.0 | 8 / 0 |
v3.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-17. This could indicate a legitimate maintainer transition or an account compromise.
v3.9.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.9.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-25. This could indicate a legitimate maintainer transition or an account compromise.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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.
v2.1.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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.