@data-fair/catalog-melodi
Melodi plugin for the Data Fair catalogs service.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:memoize | AI (phantom-deps): memoize is declared as a runtime dep; phantom-dep heuristic likely misfires on TypeScript source layout for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Niche org plugin; sparse README and no homepage are expected for internal ecosystem tooling. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is a declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:prom-client | AI (phantom-deps): prom-client is a declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@data-fair/lib-utils | AI (phantom-deps): Same org scope; declared dependency, stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.8 | 6 / 12 | |
| 0.4.5 | 6 / 12 | |
| 0.4.4 | 6 / 12 | |
| 0.4.3 | 6 / 12 | |
| 0.4.2 | 6 / 12 | |
| 0.4.1 | 6 / 12 | |
| 0.4.0 | 6 / 12 | |
| 0.2.0 | 6 / 12 | |
| 0.1.1 | 6 / 13 |
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.