← Home

@backstage/plugin-scaffolder-node

9
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Provenance attestation is not yet standard practice; absence is common and not a security concern for established ecosystem packages. ai
dependencies unvetted-dep:@backstage/types AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency for this package. ai
dependencies unvetted-dep:@isomorphic-git/pgp-plugin AI (dependencies): Official companion plugin to isomorphic-git for PGP signing; expected dependency for git operations in scaffolder. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): Official @backstage/* package from the same monorepo; stable core dependency. ai
dependencies unvetted-dep:@backstage/plugin-permission-common AI (dependencies): Official @backstage/* package from the same monorepo; stable dependency. ai
dependencies unvetted-dep:isomorphic-git AI (dependencies): isomorphic-git is a well-known, legitimate git library; expected dependency for a scaffolder node plugin doing git operations. ai
phantom-deps phantom-dep:winston AI (phantom-deps): winston is declared as a runtime dep and re-exported/used indirectly in Backstage logging infrastructure; not a security concern. ai
phantom-deps phantom-dep:winston-transport AI (phantom-deps): winston-transport is a companion to winston; same indirect usage pattern in Backstage logging; not a security concern. ai
bogus-package bogus-package AI (bogus-package): Backstage packages typically have minimal READMEs pointing to backstage.io docs and omit npm keywords; not indicative of spam or malicious intent. ai
dependencies unvetted-dep:@backstage/plugin-scaffolder-common AI (dependencies): Official @backstage/* sibling package in the same plugin family; stable dependency. ai

Versions (showing 9 of 9)

Version Deps Published
0.13.3 21 / 5
0.13.2 21 / 5
0.13.1 21 / 5
0.13.0 20 / 5
0.12.5 20 / 4
0.12.4 20 / 4
0.12.3 20 / 4
0.11.3 20 / 4
0.11.2 20 / 4

v0.13.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.