npm PACKAGE

@backstage/backend-defaults 0.16.1

Warn

PkgFire would install this release with a warning.·Checked 5 hours ago·Published 29 August 2026

npmjs.com

Why

  • warnVulnerability

    Backstage: Improper access control in backend action invocation (fixed in 0.17.8)

  • warnVulnerability

    Backstage: Improper input validation in cloud storage URL readers (fixed in 0.17.8)

  • warnVulnerability

    Backstage: Improper preservation of access restrictions during service credential delegation (fixed in 0.17.8)

Provenance

A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.

Signature
Verified against the registry's key
Build provenance
None, and no earlier version had any

What the code does

On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.

Code reading

PkgFire's own reading of the files: what the code can do.

  • code-networkdist/alpha/entrypoints/actions/DefaultActionsService.cjs.js, dist/entrypoints/auth/plugin/PluginTokenHandler.cjs.js, dist/entrypoints/httpRouter/httpRouterServiceFactory.cjs.js, dist/entrypoints/rootHttpRouter/http/createHttpServer.cjs.js, dist/entrypoints/urlReader/lib/AzureUrlReader.cjs.js

Source patterns

Patterns found in the source, including those malware is known to use.

  • capability-filesystem-read
  • capability-network-download
  • capability-network-outbound
  • capability-process-hooks
  • capability-process-schedule

Other checked releases

Check every dependency before it installs

This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.

Start free How it works