← Home

@backstage-community/plugin-catalog-backend-module-linguist-tags-processor

npm Repository

The linguist-tags-processor backend module for the catalog plugin.

29
Versions
Apache-2.0
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:@backstage/config AI (phantom-deps): Config-only reference in config.d.ts schema; not a direct import — stable false positive for this package. ai
phantom-deps phantom-dep:@backstage-community/plugin-linguist-common AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires due to indirect import pattern, stable false positive. ai

Versions (showing 29 of 29)

Version Deps Published
0.23.0 7 / 5
0.22.0 7 / 5
0.21.0 7 / 5
0.20.0 7 / 5
0.19.0 7 / 5
0.18.0 7 / 5
0.17.0 7 / 5
0.16.0 7 / 5
0.15.0 7 / 5
0.14.0 7 / 5
0.13.0 7 / 5
0.12.1 7 / 5
0.12.0 7 / 5
0.11.0 7 / 5
0.10.0 7 / 5
0.9.0 7 / 5
0.8.0 7 / 4
0.7.0 7 / 4
0.6.0 7 / 4
0.5.0 7 / 4
0.4.0 7 / 4
0.3.0 7 / 4
0.2.2 7 / 5
0.2.1 7 / 5
0.2.0 8 / 5
0.1.5 8 / 5
0.1.4 8 / 5
0.1.3 8 / 5
0.1.2 8 / 5

v0.23.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.22.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.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.