@backstage/plugin-techdocs-module-addons-contrib
Plugin module for contributed TechDocs Addons
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:photoswipe | AI (dependencies): photoswipe is a legitimate, well-known JavaScript lightbox library; appropriate dependency for a TechDocs frontend addon plugin. | ai | |
| dependencies | unvetted-dep:@react-hookz/web | AI (dependencies): @react-hookz/web is a legitimate React hooks utility library; appropriate for a frontend plugin in the Backstage ecosystem. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): @material-ui/icons is a standard Material UI icon library widely used across the Backstage ecosystem. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-techdocs-react | AI (dependencies): First-party Backstage package from the same monorepo; expected dependency for a TechDocs addon module. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages historically published without Sigstore provenance; package legitimacy is well-established through age, download volume, and monorepo origin. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.1.36 | 11 / 12 | |
| 1.1.35 | 11 / 12 | |
| 1.1.34 | 11 / 12 | |
| 1.1.33 | 11 / 12 | |
| 1.1.32 | 11 / 12 | |
| 1.1.31 | 11 / 12 | |
| 1.1.30 | 11 / 11 | |
| 1.1.29 | 11 / 11 | |
| 1.1.28 | 11 / 11 | |
| 1.1.27 | 11 / 11 | |
| 1.1.26 | 11 / 11 | |
| 1.1.25 | 11 / 11 | |
| 1.1.24 | 11 / 11 |
v1.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
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.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
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.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.