@backstage/plugin-auth-backend-module-aws-alb-provider Apache-2.0 42 versions

@backstage/plugin-auth-backend-module-aws-alb-provider

npm Repository Homepage

The aws-alb provider module for the Backstage auth backend.

42

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

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@backstage/plugin-auth-backend	AI (phantom-deps): Backstage plugin modules commonly declare the parent plugin as a dependency for type compatibility without directly importing it. This is a stable pattern in the Backstage monorepo.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/errors	AI (dependencies): Official Backstage monorepo package; well-established, high-download ecosystem dependency. Unvetted status is a registry coverage gap, not a risk signal.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-auth-node	AI (dependencies): Official Backstage monorepo package; well-established ecosystem dependency. Unvetted status is a registry coverage gap.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/backend-plugin-api	AI (dependencies): Official Backstage monorepo package; well-established ecosystem dependency. Unvetted status is a registry coverage gap.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-auth-backend	AI (dependencies): Official Backstage monorepo package; well-established ecosystem dependency. Unvetted status is a registry coverage gap.	ai	2026/04/25
dependencies	unvetted-dep:node-cache	AI (dependencies): node-cache is a popular, stable npm caching library with millions of downloads. No known security concerns.	ai	2026/04/25

Versions (showing 42 of 42)

Version	Deps	Published
0.4.18	7 / 6	2026-07-14
0.4.17	7 / 6	2026-06-16
0.4.16	7 / 6	2026-05-19
0.4.15	7 / 6	2026-04-14
0.4.14	7 / 6	2026-03-17
0.4.13	7 / 6	2026-02-17
0.4.12	7 / 6	2026-01-28
0.4.11	7 / 6	2026-01-20
0.4.10	7 / 6	2025-12-16
0.4.9	7 / 6	2025-11-18
0.4.8	7 / 6	2025-10-14
0.4.7	7 / 6	2025-09-16
0.4.6	7 / 6	2025-08-19
0.4.5	7 / 6	2025-07-15
0.4.4	7 / 6	2025-06-17
0.4.3	7 / 6	2025-05-20
0.4.2	6 / 6	2025-04-15
0.4.1	6 / 6	2025-03-18
0.4.0	6 / 6	2025-02-18
0.3.2	6 / 5	2025-01-14
0.3.1	6 / 5	2024-12-17
0.3.0	7 / 5	2024-11-19
0.2.1	8 / 5	2024-10-15
0.2.0	8 / 5	2024-09-17
0.1.17	8 / 5	2024-08-27
0.1.16	8 / 5	2024-08-26
0.1.15	8 / 5	2024-08-20
0.1.14	8 / 5	2024-07-16
0.1.13	8 / 5	2024-06-26
0.1.12	8 / 5	2024-06-19
0.1.11	8 / 5	2024-06-18
0.1.10	8 / 5	2024-05-14
0.1.9	8 / 5	2024-04-16
0.1.8	8 / 5	2024-03-27
0.1.7	8 / 5	2024-03-22
0.1.6	8 / 5	2024-03-22
0.1.5	8 / 5	2024-03-19
0.1.4	8 / 5	2024-03-01
0.1.3	8 / 5	2024-02-23
0.1.2	8 / 5	2024-02-22
0.1.1	8 / 5	2024-02-21
0.1.0	8 / 5	2024-02-20

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.17

1 finding

LOW No provenance attestation provenance

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

v0.1.16

1 finding

LOW No provenance attestation provenance

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

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.14

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

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

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.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.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.