@bcgov/plugin-catalog-backend-module-bc-data-catalogue
The bc-data-catalogue backend module for the catalog plugin.
2
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
jleachshellyxuehanparcjasonakroon3rbc-gov-common-servicesnicoledegreefqqnluaqjujagadgbossty2kmichael.nelson.gov.bc.camgranboissheaphillipscitzcodemvpsidmclaughlintaylorfriesbradenmitchellirfan.charaniastoewsmkernohanbcsupriya-aroradanebenalomprakashmishragalen.graymarcelmuellerfbarretajimmypalelil
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 reflects monorepo/workspace versioning convention for a BC Gov Backstage plugin, not a throwaway package. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Backstage config is commonly declared as a dep for type resolution without direct imports; stable false positive for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:@bcgov/plugin-catalog-common-bc-data-catalogue | AI (phantom-deps): Sibling monorepo package with workspace:* constraint; phantom-dep heuristic unreliable for workspace deps. | ai |
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.