← Home

@backstage-community/search-backend-module-adr

31
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

patriko

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:luxon AI (phantom-deps): Runtime dependency for date handling; used in config processing, not direct imports. ai
phantom-deps phantom-dep:marked AI (phantom-deps): Runtime dependency for markdown parsing; used in config processing, not direct imports. ai
phantom-deps phantom-dep:@backstage/config AI (phantom-deps): Backstage plugin peer-dependency pattern; stable across versions. ai

Versions (showing 31 of 31)

Version Deps Published
0.21.0 10 / 1
0.20.0 10 / 1
0.19.0 10 / 1
0.18.0 10 / 1
0.17.0 10 / 1
0.16.1 10 / 1
0.16.0 10 / 1
0.15.0 10 / 1
0.14.0 10 / 1
0.13.1 10 / 1
0.13.0 12 / 2
0.12.0 12 / 2
0.11.0 12 / 2
0.10.0 12 / 2
0.9.0 12 / 2
0.8.0 12 / 2
0.7.0 12 / 2
0.6.0 12 / 2
0.5.1 12 / 2
0.5.0 12 / 2
0.4.0 12 / 2
0.3.2 12 / 2
0.3.1 12 / 2
0.3.0 13 / 2
0.2.1 13 / 2
0.2.0 13 / 2
0.1.4 14 / 2
0.1.3 14 / 2
0.1.2 14 / 2
0.1.1 14 / 2
0.1.0 14 / 2

v0.21.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

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

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.