← Home

@backstage/plugin-catalog-backend-module-ldap

A Backstage catalog backend module that helps integrate towards LDAP

12
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

patrikofrebenmarcuseide

Keywords

backstage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 12 of 12)

Version Deps Published
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

v0.12.5

1 finding
INFO No provenance attestation provenance

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

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

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.