@backstage/plugin-techdocs-react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/plugin-techdocs-common | AI (dependencies): First-party Backstage package in the same plugin family, explicitly listed in the pluginPackages manifest. Not a suspicious third-party dependency. | ai | |
| phantom-deps | phantom-dep:react-helmet | AI (phantom-deps): react-helmet is a declared runtime dependency in package.json; phantom-dep flag is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): @material-ui/core is a declared runtime dependency in package.json; phantom-dep flag is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/core-components | AI (phantom-deps): @backstage/core-components is a declared runtime dependency in package.json; phantom-dep flag is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages are published from the official monorepo; lack of Sigstore provenance is acceptable given strong ecosystem identity signals. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.3.11 | 12 / 9 | |
| 1.3.10 | 13 / 9 | |
| 1.3.9 | 13 / 9 | |
| 1.3.8 | 13 / 9 | |
| 1.3.7 | 13 / 9 | |
| 1.3.6 | 13 / 9 | |
| 1.3.5 | 13 / 9 | |
| 1.3.4 | 13 / 9 | |
| 1.3.3 | 13 / 9 | |
| 1.3.2 | 13 / 9 | |
| 1.3.1 | 13 / 9 | |
| 1.3.0 | 13 / 9 | |
| 1.2.17 | 12 / 9 |
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.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.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.