@backstage/plugin-app-node
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package from the official Backstage project; short README and no keywords are expected for internal node-library packages. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is intentionally listed as a runtime dep in some Backstage packages for type augmentation; not a real phantom dep concern. | 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 for this well-established project. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.1.47 | 5 / 1 | |
| 0.1.46 | 5 / 1 | |
| 0.1.45 | 5 / 1 | |
| 0.1.44 | 5 / 1 | |
| 0.1.43 | 5 / 1 | |
| 0.1.42 | 5 / 1 | |
| 0.1.41 | 5 / 1 | |
| 0.1.40 | 5 / 1 | |
| 0.1.39 | 5 / 1 | |
| 0.1.38 | 5 / 1 | |
| 0.1.37 | 5 / 1 | |
| 0.1.36 | 5 / 1 | |
| 0.1.35 | 5 / 1 | |
| 0.1.34 | 5 / 1 | |
| 0.1.33 | 5 / 1 | |
| 0.1.32 | 5 / 1 | |
| 0.1.31 | 5 / 1 | |
| 0.1.30 | 5 / 1 | |
| 0.1.29 | 5 / 1 | |
| 0.1.28 | 5 / 1 | |
| 0.1.27 | 5 / 1 | |
| 0.1.26 | 5 / 1 | |
| 0.1.25 | 5 / 1 | |
| 0.1.24 | 5 / 1 | |
| 0.1.23 | 5 / 1 | |
| 0.1.22 | 5 / 1 | |
| 0.1.21 | 5 / 1 | |
| 0.1.20 | 5 / 1 | |
| 0.1.19 | 5 / 1 | |
| 0.1.18 | 5 / 1 | |
| 0.1.17 | 5 / 1 | |
| 0.1.16 | 5 / 1 | |
| 0.1.15 | 5 / 1 | |
| 0.1.14 | 5 / 1 | |
| 0.1.13 | 5 / 1 | |
| 0.1.12 | 5 / 1 | |
| 0.1.11 | 5 / 1 | |
| 0.1.10 | 5 / 1 | |
| 0.1.9 | 3 / 1 | |
| 0.1.8 | 3 / 1 | |
| 0.1.7 | 3 / 1 | |
| 0.1.6 | 3 / 1 | |
| 0.1.5 | 3 / 1 | |
| 0.1.4 | 3 / 1 | |
| 0.1.3 | 3 / 1 | |
| 0.1.2 | 3 / 1 | |
| 0.1.1 | 3 / 1 | |
| 0.1.0 | 3 / 1 |
v0.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.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.