@backstage/plugin-auth-node No license 73 versions

@backstage/plugin-auth-node

npm Repository Homepage

73

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, 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:winston	AI (phantom-deps): Likely used via bundled build output; no malicious indicator.	ai	2026/07/21
phantom-deps	phantom-dep:@backstage/config	AI (phantom-deps): Same-org monorepo dep, standard FP pattern.	ai	2026/07/21
phantom-deps	phantom-dep:@backstage/catalog-model	AI (phantom-deps): Same-org monorepo dep, standard FP pattern.	ai	2026/07/21
phantom-deps	phantom-dep:@backstage/backend-common	AI (phantom-deps): Same-org monorepo dep, standard FP pattern.	ai	2026/07/21
dependencies	unvetted-dep:@backstage/errors	AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/types	AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package.	ai	2026/04/25
dependencies	unvetted-dep:@types/passport	AI (dependencies): @types/passport is a well-known DefinitelyTyped package; stable false positive for this auth plugin.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/backend-plugin-api	AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package.	ai	2026/04/25
phantom-deps	phantom-dep:@types/passport	AI (phantom-deps): @types/passport used for type augmentation in passport-based auth plugins; standard pattern.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Monorepo packages commonly lack standalone descriptions, keywords, and detailed READMEs; not indicative of spam or malice for this established Backstage package.	ai	2026/04/25
phantom-deps	phantom-dep:@types/express	AI (phantom-deps): @types/express is listed for TypeScript declaration merging in Express-based plugins; standard pattern in Backstage.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/catalog-client	AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/catalog-model	AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/config	AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package.	ai	2026/04/25

Versions (showing 73 of 73)

Version	Deps	Published
0.7.3	15 / 7	2026-07-14
0.7.2	15 / 7	2026-06-16
0.7.1	15 / 7	2026-05-19
0.7.0	15 / 9	2026-04-14
0.6.14	15 / 9	2026-03-17
0.6.13	15 / 9	2026-02-17
0.6.12	15 / 9	2026-01-28
0.6.11	15 / 9	2026-01-20
0.6.10	15 / 9	2025-12-16
0.6.9	15 / 9	2025-11-18
0.6.8	15 / 9	2025-10-14
0.6.7	15 / 9	2025-09-16
0.6.6	15 / 9	2025-08-19
0.6.5	15 / 9	2025-07-15
0.6.4	15 / 9	2025-06-17
0.6.3	15 / 9	2025-05-20
0.6.2	15 / 9	2025-04-15
0.6.1	15 / 9	2025-03-18
0.6.0	15 / 9	2025-02-18
0.5.6	17 / 9	2025-01-14
0.5.5	17 / 8	2024-12-17
0.5.4	18 / 8	2024-11-19
0.5.3	18 / 8	2024-10-15
0.5.2	17 / 8	2024-09-17
0.5.1	17 / 8	2024-08-27
0.5.0	17 / 8	2024-08-20
0.4.17	17 / 8	2024-07-16
0.4.16	17 / 8	2024-06-26
0.4.15	17 / 8	2024-06-19
0.4.14	17 / 8	2024-06-18
0.4.13	17 / 8	2024-05-14
0.4.12	17 / 8	2024-04-16
0.4.11	17 / 8	2024-03-27
0.4.10	17 / 8	2024-03-22
0.4.9	17 / 8	2024-03-19
0.4.8	17 / 8	2024-03-01
0.4.7	17 / 8	2024-02-23
0.4.6	17 / 8	2024-02-22
0.4.5	17 / 8	2024-02-21
0.4.4	17 / 8	2024-02-20
0.4.3	17 / 8	2024-01-16
0.4.2	17 / 8	2023-12-19
0.4.1	17 / 8	2023-11-14
0.4.0	17 / 8	2023-10-17
0.3.2	17 / 8	2023-10-04
0.3.0	17 / 8	2023-09-19
0.2.19	8 / 5	2023-08-23
0.2.18	8 / 5	2023-08-21
0.2.17	8 / 5	2023-08-15
0.2.16	8 / 5	2023-07-18
0.2.15	8 / 5	2023-06-20
0.2.14	8 / 5	2023-05-16
0.2.13	8 / 5	2023-04-18
0.2.12	8 / 5	2023-03-14
0.2.11	8 / 5	2023-02-14
0.2.10	8 / 5	2023-01-17
0.2.9	8 / 5	2023-01-17
0.2.8	8 / 5	2022-12-20
0.2.7	8 / 5	2022-11-15
0.2.6	8 / 5	2022-10-18
0.2.5	8 / 5	2022-09-20
0.2.4	6 / 4	2022-08-16
0.2.3	6 / 4	2022-07-19
0.2.2	6 / 4	2022-06-14
0.2.1	6 / 4	2022-05-17
0.2.0	6 / 3	2022-04-19
0.1.6	7 / 3	2022-03-17
0.1.5	7 / 3	2022-03-10
0.1.4	7 / 3	2022-03-03
0.1.3	7 / 3	2022-02-24
0.1.2	7 / 3	2022-02-17
0.1.1	7 / 3	2022-02-17
0.1.0	7 / 3	2022-02-10

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

1 finding

LOW No provenance attestation provenance

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

v0.5.5

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

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.5.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.5.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.5.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.5.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.4.17

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

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

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

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

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

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

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.4.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.4.9

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

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

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

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

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

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.4.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.4.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.4.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.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.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.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.19

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.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.2.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.2.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.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.6

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

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

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