@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 — the axios compromise (March 2026) relied on exactly this gap.
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 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
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.34
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.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.