@backstage/plugin-catalog-backend-module-scaffolder-entity-model
Adds support for the scaffolder specific entity model (e.g. the Template kind) to the catalog backend plugin.
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-packages in the Backstage project routinely lack per-package keywords and verbose READMEs; this is a structural pattern, not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages are published from a well-known GitHub monorepo; absence of Sigstore provenance is not a risk signal for this established project. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.20 | 5 / 2 | |
| 0.2.19 | 5 / 2 | |
| 0.2.18 | 5 / 2 | |
| 0.2.17 | 5 / 2 | |
| 0.2.16 | 5 / 2 | |
| 0.2.15 | 5 / 2 | |
| 0.2.14 | 5 / 2 | |
| 0.2.13 | 5 / 2 | |
| 0.2.12 | 5 / 2 | |
| 0.2.11 | 5 / 2 | |
| 0.2.10 | 5 / 2 | |
| 0.2.9 | 5 / 2 | |
| 0.2.8 | 5 / 2 |
v0.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.