fumadocs-openapi
Generate MDX docs for your OpenAPI spec
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fumadocs/api-docs | AI (dependencies): First-party fumadocs org package; consistent with internal refactor of this well-established ecosystem. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lucide-react is a well-known icon library; @fumari/stf is from the same trusted org as existing @fumari deps. | ai | |
| dependencies | unvetted-dep:@fumadocs/ui | AI (dependencies): First-party fumadocs ecosystem package; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@fumari/json-schema-to-typescript | AI (dependencies): @fumari/* is the package author's own org namespace; consistent with other accepted @fumari deps in this package. | ai | |
| phantom-deps | phantom-dep:tinyglobby | AI (phantom-deps): tinyglobby is a declared runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Fumadocs packages consistently lack provenance; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@fumari/json-schema-ts | AI (dependencies): @fumari namespace matches package author Fuma Nama; own scoped dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@fumari/stf | AI (dependencies): @fumari namespace matches package author Fuma Nama; own scoped dep, not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): @radix-ui/react-slot is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 11.0.2 | 14 / 13 | |
| 11.0.1 | 14 / 13 | |
| 11.0.0 | 14 / 13 | |
| 10.10.3 | 15 / 17 | |
| 10.10.2 | 15 / 17 | |
| 10.10.1 | 15 / 17 | |
| 10.10.0 | 16 / 17 | |
| 10.9.1 | 16 / 17 | |
| 10.9.0 | 16 / 17 | |
| 10.8.6 | 16 / 17 | |
| 10.8.5 | 16 / 17 | |
| 10.8.4 | 17 / 16 | |
| 10.8.3 | 18 / 15 | |
| 10.8.1 | 18 / 15 | |
| 10.8.0 | 18 / 15 | |
| 10.7.1 | 18 / 15 | |
| 10.7.0 | 18 / 15 | |
| 10.6.8 | 20 / 14 | |
| 10.6.7 | 24 / 13 | |
| 10.6.6 | 23 / 13 | |
| 10.6.5 | 23 / 13 | |
| 10.6.4 | 23 / 13 | |
| 10.6.3 | 23 / 13 | |
| 10.6.2 | 23 / 13 | |
| 10.6.1 | 23 / 13 | |
| 10.6.0 | 23 / 14 | |
| 10.5.0 | 23 / 14 | |
| 10.4.1 | 23 / 14 | |
| 10.4.0 | 23 / 14 | |
| 10.3.18 | 22 / 13 | |
| 10.3.17 | 22 / 13 | |
| 10.3.16 | 21 / 14 | |
| 10.3.15 | 21 / 14 | |
| 10.3.14 | 21 / 14 | |
| 10.3.13 | 22 / 13 | |
| 10.3.10 | 22 / 13 | |
| 10.3.8 | 22 / 13 | |
| 10.3.6 | 22 / 13 | |
| 10.3.5 | 21 / 14 | |
| 10.3.1 | 21 / 13 | |
| 10.2.6 | 21 / 13 | |
| 10.2.4 | 20 / 13 | |
| 10.2.2 | 19 / 13 | |
| 10.2.0 | 20 / 13 | |
| 10.1.4 | 18 / 13 | |
| 10.1.3 | 18 / 13 | |
| 10.1.2 | 18 / 13 | |
| 10.1.1 | 18 / 13 | |
| 10.1.0 | 18 / 13 | |
| 10.0.11 | 22 / 11 | |
| 10.0.10 | 22 / 11 | |
| 10.0.8 | 22 / 11 | |
| 10.0.7 | 22 / 11 | |
| 10.0.6 | 22 / 11 | |
| 10.0.4 | 22 / 11 | |
| 10.0.3 | 22 / 11 | |
| 10.0.0 | 22 / 11 | |
| 9.7.3 | 22 / 11 | |
| 9.7.2 | 22 / 11 |
v11.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.