@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Types package loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:jss | AI (phantom-deps): Used transitively by @material-ui/styles theming; common FP for CSS-in-JS deps. | ai | |
| phantom-deps | phantom-dep:@material-ui/lab | AI (phantom-deps): MUI lab components used via re-exports; typical phantom-dep FP. | ai | |
| phantom-deps | phantom-dep:@material-ui/styles | AI (phantom-deps): Theming dep used indirectly; typical phantom-dep FP. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): Well-known MUI package, not a security concern. | ai | |
| 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 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.3.13 | 12 / 9 | |
| 1.3.12 | 12 / 9 | |
| 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 | |
| 1.2.16 | 12 / 9 | |
| 1.2.15 | 12 / 9 | |
| 1.2.14 | 11 / 9 | |
| 1.2.13 | 11 / 9 | |
| 1.2.12 | 11 / 9 | |
| 1.2.11 | 11 / 9 | |
| 1.2.10 | 11 / 9 | |
| 1.2.9 | 11 / 9 | |
| 1.2.8 | 12 / 5 | |
| 1.2.7 | 12 / 5 | |
| 1.2.6 | 12 / 5 | |
| 1.2.5 | 12 / 5 | |
| 1.2.4 | 12 / 5 | |
| 1.2.3 | 12 / 5 | |
| 1.2.2 | 12 / 5 | |
| 1.2.1 | 12 / 5 | |
| 1.2.0 | 12 / 5 | |
| 1.1.16 | 12 / 5 | |
| 1.1.15 | 12 / 5 | |
| 1.1.13 | 13 / 5 | |
| 1.1.8 | 13 / 6 | |
| 1.1.7 | 13 / 6 | |
| 1.0.4 | 12 / 6 | |
| 1.0.0 | 12 / 4 |
v1.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
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.1.15
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.1.13
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.1.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.1.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.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.
v1.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.