@backstage/plugin-api-docs
A Backstage plugin that helps represent API entities in the frontend
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:isomorphic-form-data | AI (phantom-deps): Declared dependency used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@material-ui/icons | AI (phantom-deps): @material-ui/icons is the standard MUI icons package; phantom detection is a false positive for this well-known Backstage dependency. | ai | |
| dependencies | unvetted-dep:@asyncapi/react-component | AI (dependencies): @asyncapi/react-component is the official AsyncAPI React renderer; expected for an API docs plugin supporting AsyncAPI specs. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): @material-ui/lab is a well-known React UI library, expected dependency for Backstage frontend plugins using MUI v4. | ai | |
| phantom-deps | phantom-dep:graphql-config | AI (phantom-deps): graphql-config is a standard GraphQL tooling package; declared for config file usage, not a security concern. | ai | |
| phantom-deps | phantom-dep:graphql-ws | AI (phantom-deps): graphql-ws is a legitimate GraphQL subscription transport; declared for consumer use in config, not a security concern. | ai | |
| dependencies | unvetted-dep:swagger-ui-react | AI (dependencies): swagger-ui-react is the official Swagger UI React wrapper; expected for an API docs plugin rendering OpenAPI specs. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.14.1 | 19 / 16 | |
| 0.14.0 | 19 / 16 | |
| 0.13.5 | 19 / 16 | |
| 0.13.4 | 18 / 15 | |
| 0.13.3 | 18 / 14 | |
| 0.13.2 | 18 / 14 | |
| 0.13.1 | 19 / 14 | |
| 0.13.0 | 19 / 14 | |
| 0.12.11 | 20 / 14 | |
| 0.12.10 | 20 / 14 | |
| 0.12.9 | 20 / 14 | |
| 0.12.8 | 20 / 14 |
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.