@backstage/plugin-catalog-backend-module-incremental-ingestion
An entity provider for streaming large asset sources into the catalog
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org @backstage scoped dep; phantom usage is expected in Backstage monorepo packages where deps may be type-only or transitively used. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-defaults | AI (phantom-deps): Same-org @backstage scoped dep; phantom usage is expected in Backstage monorepo packages. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-backend | AI (phantom-deps): Same-org @backstage scoped dep; phantom usage is expected in Backstage monorepo packages. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-common | AI (phantom-deps): Same-org @backstage scoped dep; phantom usage is expected in Backstage monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): Backstage's npm release pipeline does not use Sigstore provenance; this is consistent across all @backstage/* packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.7.12 | 13 / 3 | |
| 0.7.11 | 15 / 3 | |
| 0.7.10 | 15 / 3 | |
| 0.7.9 | 16 / 3 | |
| 0.7.8 | 16 / 3 | |
| 0.7.7 | 16 / 3 | |
| 0.7.6 | 16 / 4 | |
| 0.7.5 | 16 / 4 | |
| 0.7.4 | 16 / 4 | |
| 0.7.3 | 16 / 4 | |
| 0.7.2 | 16 / 4 | |
| 0.7.1 | 16 / 4 | |
| 0.7.0 | 16 / 4 |
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.