@backstage/frontend-app-api Apache-2.0 44 versions

@backstage/frontend-app-api

npm Repository

44

Versions

Apache-2.0

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Framework-scoped type dep, loaded by convention.	ai	2026/07/21
phantom-deps	phantom-dep:@backstage/plugin-graphiql	AI (phantom-deps): Same-org dependency, re-exported not directly imported.	ai	2026/07/21
phantom-deps	phantom-dep:@backstage/types	AI (phantom-deps): Same-org type-only dependency, common false positive.	ai	2026/07/21
dependencies	unvetted-dep:@backstage/plugin-graphiql	AI (dependencies): Official first-party Backstage plugin, same org/monorepo.	ai	2026/07/21
npm-metadata	suspicious-initial-version	AI (npm-metadata): Backstage's monorepo uses 0.0.0 as intentional version convention, not throwaway signal.	ai	2026/07/21
dependencies	unvetted-dep:@backstage/version-bridge	AI (dependencies): @backstage/version-bridge is a legitimate same-org Backstage package; it is a stable dependency across all Backstage frontend packages.	ai	2026/04/27
phantom-deps	phantom-dep:@backstage/errors	AI (phantom-deps): Same-org @backstage package used transitively in a monorepo build artifact; not indicative of risk.	ai	2026/04/27
bogus-package	bogus-package	AI (bogus-package): Backstage monorepo packages routinely lack keywords, detailed READMEs, and descriptions on npm — this is a structural pattern, not a spam indicator.	ai	2026/04/25
npm-metadata	no-description	AI (npm-metadata): Backstage monorepo packages commonly omit npm descriptions; not indicative of malicious intent for this well-established package.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/core-plugin-api	AI (phantom-deps): Same-org Backstage dependency; indirect usage is expected in the Backstage monorepo pattern.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/version-bridge	AI (phantom-deps): Same-org Backstage dependency; indirect usage is expected in the Backstage monorepo pattern.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/core-app-api	AI (phantom-deps): Same-org Backstage dependency; indirect usage via type re-exports or config is expected in the Backstage monorepo pattern.	ai	2026/04/25
phantom-deps	phantom-dep:zod	AI (phantom-deps): zod is declared as a runtime dep and referenced in config schema; phantom detection may miss indirect usage patterns in Backstage monorepo packages.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/frontend-defaults	AI (phantom-deps): Same-org Backstage dependency; indirect usage is expected in the Backstage monorepo pattern.	ai	2026/04/25

Versions (showing 44 of 44)

Version	Deps	Published
0.16.6	11 / 11	2026-07-14
0.16.5	11 / 11	2026-06-26
0.16.4	11 / 11	2026-06-16
0.16.3	11 / 11	2026-05-19
0.16.2	11 / 11	2026-04-14
0.16.1	11 / 11	2026-03-20
0.16.0	11 / 11	2026-03-17
0.15.0	10 / 10	2026-02-17
0.14.1	10 / 10	2026-01-28
0.14.0	10 / 10	2026-01-20
0.13.3	10 / 10	2025-12-16
0.13.2	10 / 10	2025-11-18
0.13.1	10 / 10	2025-10-14
0.13.0	10 / 10	2025-09-16
0.12.0	10 / 10	2025-08-19
0.11.4	10 / 9	2025-07-15
0.11.3	10 / 9	2025-06-17
0.11.2	10 / 9	2025-05-20
0.11.1	10 / 9	2025-04-15
0.11.0	10 / 9	2025-03-18
0.10.5	10 / 9	2025-02-18
0.10.4	10 / 9	2025-01-14
0.10.3	10 / 9	2024-12-17
0.10.2	10 / 9	2024-11-21
0.10.1	10 / 9	2024-11-19
0.10.0	10 / 9	2024-10-15
0.9.0	10 / 5	2024-09-17
0.8.0	13 / 4	2024-08-20
0.7.4	13 / 4	2024-07-24
0.7.3	13 / 4	2024-07-16
0.7.2	13 / 4	2024-06-26
0.7.1	13 / 4	2024-06-18
0.7.0	13 / 4	2024-05-14
0.6.4	13 / 4	2024-04-16
0.6.3	13 / 4	2024-03-27
0.6.2	13 / 4	2024-03-22
0.6.1	13 / 4	2024-03-19
0.6.0	13 / 4	2024-02-20
0.5.0	13 / 4	2024-01-16
0.4.0	13 / 4	2023-12-19
0.3.0	13 / 4	2023-11-14
0.2.0	13 / 4	2023-10-17
0.1.0	10 / 2	2023-09-19
0.0.0	6 / 3	2023-09-08

v0.16.6

1 finding

LOW No provenance attestation provenance

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

v0.16.5

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.5

1 finding

LOW No provenance attestation provenance

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

v0.10.4

1 finding

LOW No provenance attestation provenance

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

v0.10.3

1 finding

LOW No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

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.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

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.3.0

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.2.0

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.1.0

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.0.0

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.