@backstage/plugin-auth-node
Supply chain provenance
Status for the latest visible version.
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
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 | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org monorepo dep, standard FP pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Same-org monorepo dep, standard FP pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-common | AI (phantom-deps): Same-org monorepo dep, standard FP pattern. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package. | ai | |
| dependencies | unvetted-dep:@types/passport | AI (dependencies): @types/passport is a well-known DefinitelyTyped package; stable false positive for this auth plugin. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package. | ai | |
| phantom-deps | phantom-dep:@types/passport | AI (phantom-deps): @types/passport used for type augmentation in passport-based auth plugins; standard pattern. | ai | |
| 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 | |
| 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 | |
| dependencies | unvetted-dep:@backstage/catalog-client | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for this package. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 15 / 7 | |
| 0.7.2 | 15 / 7 | |
| 0.7.1 | 15 / 7 | |
| 0.7.0 | 15 / 9 | |
| 0.6.14 | 15 / 9 | |
| 0.6.13 | 15 / 9 | |
| 0.6.12 | 15 / 9 | |
| 0.6.11 | 15 / 9 | |
| 0.6.10 | 15 / 9 | |
| 0.6.9 | 15 / 9 | |
| 0.6.8 | 15 / 9 | |
| 0.6.7 | 15 / 9 | |
| 0.6.6 | 15 / 9 | |
| 0.6.5 | 15 / 9 | |
| 0.6.4 | 15 / 9 | |
| 0.6.3 | 15 / 9 | |
| 0.6.2 | 15 / 9 | |
| 0.6.1 | 15 / 9 | |
| 0.6.0 | 15 / 9 | |
| 0.5.6 | 17 / 9 | |
| 0.5.5 | 17 / 8 | |
| 0.5.4 | 18 / 8 | |
| 0.5.3 | 18 / 8 | |
| 0.5.2 | 17 / 8 | |
| 0.5.1 | 17 / 8 | |
| 0.5.0 | 17 / 8 | |
| 0.4.17 | 17 / 8 | |
| 0.4.16 | 17 / 8 | |
| 0.4.15 | 17 / 8 | |
| 0.4.14 | 17 / 8 | |
| 0.4.13 | 17 / 8 | |
| 0.4.12 | 17 / 8 | |
| 0.4.11 | 17 / 8 | |
| 0.4.10 | 17 / 8 | |
| 0.4.9 | 17 / 8 | |
| 0.4.8 | 17 / 8 | |
| 0.4.7 | 17 / 8 | |
| 0.4.6 | 17 / 8 | |
| 0.4.5 | 17 / 8 | |
| 0.4.4 | 17 / 8 | |
| 0.4.3 | 17 / 8 | |
| 0.4.2 | 17 / 8 | |
| 0.4.1 | 17 / 8 | |
| 0.4.0 | 17 / 8 | |
| 0.3.2 | 17 / 8 | |
| 0.3.0 | 17 / 8 | |
| 0.2.19 | 8 / 5 | |
| 0.2.18 | 8 / 5 | |
| 0.2.17 | 8 / 5 | |
| 0.2.16 | 8 / 5 | |
| 0.2.15 | 8 / 5 |
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.