@backstage/plugin-techdocs-backend
The Backstage backend plugin that renders technical documentation for your components
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:@backstage/plugin-search-backend-module-techdocs | AI (phantom-deps): Same-org re-export pattern in Backstage plugins; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-defaults | AI (phantom-deps): Same-org re-export pattern in Backstage plugins; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-common | AI (phantom-deps): Same-org re-export pattern in Backstage plugins; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-techdocs-common | AI (phantom-deps): Same-org re-export pattern in Backstage plugins; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-common | AI (phantom-deps): Same-org re-export pattern in Backstage plugins; stable. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-file reference in established monorepo plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org re-export pattern in Backstage plugins; stable. | ai | |
| phantom-deps | phantom-dep:knex | AI (phantom-deps): knex is declared as a dependency and referenced in config schema/types; phantom detection is a false positive for this plugin's indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a standard backend dependency used indirectly via router patterns in Backstage plugins; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-client | AI (phantom-deps): Same-org @backstage/* dependency used indirectly; phantom detection is a false positive for this monorepo plugin structure. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages are published via CI pipeline; lack of Sigstore provenance is consistent across the entire @backstage/* namespace and does not indicate risk. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 15 / 6 | |
| 2.1.7 | 15 / 6 | |
| 2.1.6 | 15 / 6 | |
| 2.1.5 | 15 / 6 | |
| 2.1.4 | 16 / 6 | |
| 2.1.3 | 16 / 6 | |
| 2.1.2 | 16 / 6 | |
| 2.1.1 | 21 / 6 | |
| 2.1.0 | 21 / 6 | |
| 2.0.5 | 20 / 6 | |
| 2.0.4 | 20 / 6 | |
| 2.0.3 | 20 / 6 | |
| 2.0.2 | 20 / 6 |
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
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.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.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.5
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.4
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.3
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.