@backstage/integration-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): Well-known, widely used UI library dependency. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Legit dep, likely used via re-exports not caught by static scan. | ai | |
| phantom-deps | phantom-dep:@material-ui/lab | AI (phantom-deps): Known Material-UI dep, common false positive in TS build output. | ai | |
| phantom-deps | phantom-dep:@backstage/theme | AI (phantom-deps): Same-org dep, standard Backstage package. | ai | |
| phantom-deps | phantom-dep:@backstage/core-components | AI (phantom-deps): Same-org dep, standard Backstage package. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): @material-ui/icons is a well-known, widely-used Material UI package; its use as a dependency in Backstage UI packages is standard and expected across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages are published without Sigstore provenance; this is consistent across all versions and not a security concern given the package's established history. | ai | |
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): @material-ui/core is a legitimate peer/dependency in the Material-UI ecosystem; phantom classification is a packaging quirk, not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages routinely lack keywords and detailed READMEs; this is a cosmetic artifact of the Backstage monorepo structure, not a spam indicator. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.2.20 | 5 / 10 | |
| 1.2.19 | 5 / 11 | |
| 1.2.18 | 5 / 11 | |
| 1.2.17 | 5 / 11 | |
| 1.2.16 | 5 / 11 | |
| 1.2.15 | 5 / 11 | |
| 1.2.14 | 5 / 11 | |
| 1.2.13 | 5 / 11 | |
| 1.2.12 | 5 / 11 | |
| 1.2.11 | 5 / 11 | |
| 1.2.10 | 5 / 11 | |
| 1.2.9 | 5 / 11 | |
| 1.2.8 | 5 / 11 | |
| 1.2.7 | 5 / 11 | |
| 1.2.6 | 5 / 11 | |
| 1.2.5 | 5 / 11 | |
| 1.2.4 | 5 / 11 | |
| 1.2.3 | 5 / 11 | |
| 1.2.2 | 5 / 11 | |
| 1.2.1 | 5 / 11 | |
| 1.2.0 | 5 / 11 | |
| 1.1.32 | 6 / 7 | |
| 1.1.31 | 6 / 7 | |
| 1.1.30 | 6 / 7 | |
| 1.1.29 | 6 / 7 | |
| 1.1.28 | 6 / 7 | |
| 1.1.27 | 6 / 7 | |
| 1.1.26 | 6 / 7 | |
| 1.1.25 | 6 / 7 | |
| 1.1.24 | 6 / 7 | |
| 1.1.23 | 6 / 7 | |
| 1.1.22 | 6 / 7 | |
| 1.1.21 | 6 / 7 | |
| 1.1.20 | 6 / 7 | |
| 1.1.19 | 10 / 8 | |
| 1.0.0 | 9 / 10 |
v1.2.20
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. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
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.20
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.19
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.