@backstage/plugin-catalog-backend-module-ldap
A Backstage catalog backend module that helps integrate towards LDAP
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/ldapjs | AI (phantom-deps): @types/ldapjs is a TypeScript type package used at compile time; phantom-dep false positive for this package. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Core Backstage package from the official monorepo; stable dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Core Backstage package from the official monorepo; stable dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Core Backstage package from the official monorepo; standard catalog dependency. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Core Backstage package from the official monorepo; standard backend plugin dependency. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Core Backstage package from the official monorepo; stable dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-common | AI (dependencies): Official Backstage catalog plugin package; expected dependency for catalog backend modules. | ai | |
| dependencies | unvetted-dep:ldapts | AI (dependencies): ldapts is a well-known LDAP client library; its use is expected and appropriate for an LDAP catalog integration plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package; lack of Sigstore provenance is common and not a risk signal for this well-known project. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Official Backstage catalog plugin package; expected dependency for catalog backend modules. | ai |
Versions (showing 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.12.7 | 9 / 2 | |
| 0.12.6 | 9 / 2 | |
| 0.12.5 | 9 / 2 | |
| 0.12.4 | 10 / 2 | |
| 0.12.3 | 10 / 2 | |
| 0.12.2 | 10 / 2 | |
| 0.12.1 | 10 / 2 | |
| 0.12.0 | 10 / 2 | |
| 0.11.10 | 11 / 2 | |
| 0.11.9 | 11 / 2 | |
| 0.11.8 | 11 / 2 | |
| 0.11.7 | 11 / 2 | |
| 0.11.6 | 11 / 2 | |
| 0.11.5 | 11 / 2 | |
| 0.11.4 | 11 / 2 | |
| 0.11.3 | 11 / 2 | |
| 0.11.2 | 11 / 2 | |
| 0.11.1 | 11 / 2 | |
| 0.11.0 | 11 / 2 | |
| 0.10.1 | 11 / 2 | |
| 0.10.0 | 11 / 2 | |
| 0.9.1 | 11 / 2 | |
| 0.9.0 | 11 / 2 | |
| 0.8.1 | 11 / 2 | |
| 0.8.0 | 11 / 2 | |
| 0.7.0 | 12 / 2 | |
| 0.6.2 | 12 / 2 | |
| 0.6.1 | 12 / 2 | |
| 0.6.0 | 12 / 2 | |
| 0.5.34 | 12 / 2 | |
| 0.5.33 | 12 / 2 | |
| 0.5.32 | 12 / 2 | |
| 0.5.31 | 12 / 2 | |
| 0.5.30 | 12 / 2 | |
| 0.5.29 | 12 / 2 | |
| 0.5.28 | 12 / 2 | |
| 0.5.27 | 12 / 2 | |
| 0.5.26 | 12 / 2 | |
| 0.5.25 | 12 / 2 | |
| 0.5.24 | 12 / 2 | |
| 0.5.23 | 12 / 2 | |
| 0.5.22 | 12 / 2 | |
| 0.5.21 | 12 / 2 | |
| 0.5.20 | 12 / 2 | |
| 0.5.19 | 12 / 2 | |
| 0.5.18 | 12 / 2 | |
| 0.5.17 | 12 / 2 | |
| 0.5.16 | 12 / 2 | |
| 0.5.15 | 12 / 2 | |
| 0.5.14 | 12 / 2 | |
| 0.5.13 | 12 / 2 | |
| 0.5.12 | 12 / 2 | |
| 0.5.11 | 12 / 2 | |
| 0.5.10 | 11 / 2 | |
| 0.5.9 | 11 / 2 | |
| 0.5.8 | 11 / 2 | |
| 0.5.7 | 11 / 2 | |
| 0.5.6 | 11 / 2 | |
| 0.5.5 | 11 / 2 | |
| 0.5.4 | 11 / 2 | |
| 0.5.3 | 11 / 2 | |
| 0.5.2 | 11 / 2 | |
| 0.5.1 | 11 / 2 | |
| 0.5.0 | 11 / 2 | |
| 0.4.3 | 11 / 2 | |
| 0.4.2 | 11 / 2 | |
| 0.4.1 | 11 / 2 | |
| 0.4.0 | 11 / 2 | |
| 0.3.15 | 9 / 2 | |
| 0.3.14 | 9 / 2 | |
| 0.3.13 | 9 / 2 | |
| 0.3.12 | 9 / 2 | |
| 0.3.11 | 9 / 2 | |
| 0.3.10 | 9 / 2 | |
| 0.3.9 | 9 / 2 | |
| 0.3.8 | 9 / 2 | |
| 0.3.7 | 9 / 2 | |
| 0.3.6 | 9 / 2 | |
| 0.3.5 | 8 / 2 | |
| 0.3.4 | 7 / 2 | |
| 0.3.3 | 7 / 2 | |
| 0.3.2 | 7 / 2 | |
| 0.3.1 | 7 / 4 | |
| 0.3.0 | 7 / 4 | |
| 0.2.2 | 7 / 4 | |
| 0.2.1 | 7 / 4 | |
| 0.2.0 | 7 / 4 | |
| 0.1.1 | 7 / 4 | |
| 0.1.0 | 7 / 4 |
v0.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.