@reltio/ria
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @reltio org package; Levenshtein match to 'koa' is a false positive for this namespace. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-sdk | AI (phantom-deps): Same-org scoped dep in a monorepo/microfrontend; stable false positive. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-module | AI (phantom-deps): Same-org scoped dep in a monorepo/microfrontend; stable false positive. | ai | |
| phantom-deps | phantom-dep:@reltio/sources | AI (phantom-deps): Same-org scoped dep in a monorepo/microfrontend; stable false positive. | ai | |
| phantom-deps | phantom-dep:@reltio/dashboard | AI (phantom-deps): Same-org scoped dep in a monorepo/microfrontend; stable false positive. | ai | |
| phantom-deps | phantom-dep:@reltio/components | AI (phantom-deps): Same-org scoped dep in a monorepo/microfrontend; stable false positive. | ai | |
| phantom-deps | phantom-dep:swr | AI (phantom-deps): Config-referenced dep in bundled package; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Config-referenced dep in bundled package; stable false positive. | ai | |
| phantom-deps | phantom-dep:rehype-raw | AI (phantom-deps): Config-referenced dep in bundled package; stable false positive. | ai | |
| phantom-deps | phantom-dep:rehype-sanitize | AI (phantom-deps): Config-referenced dep in bundled package; stable false positive. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Config-referenced dep in bundled package; stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.4.557 | 10 / 0 | |
| 1.4.556 | 10 / 0 | |
| 1.4.555 | 10 / 0 | |
| 1.4.554 | 10 / 0 | |
| 1.4.553 | 10 / 0 | |
| 1.4.552 | 10 / 0 | |
| 1.4.551 | 10 / 0 | |
| 1.4.550 | 10 / 0 | |
| 1.4.549 | 10 / 0 | |
| 1.4.548 | 10 / 0 | |
| 1.4.547 | 10 / 0 | |
| 1.4.546 | 10 / 0 | |
| 1.4.545 | 10 / 0 | |
| 1.4.540 | 10 / 0 | |
| 1.4.539 | 10 / 0 | |
| 1.4.538 | 10 / 0 | |
| 1.4.537 | 10 / 0 | |
| 1.4.536 | 10 / 0 | |
| 1.4.535 | 10 / 0 | |
| 1.4.534 | 10 / 0 | |
| 1.4.533 | 10 / 0 |
v1.4.557
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.556
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.555
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.554
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.553
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.552
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.551
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.550
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.549
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.548
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.547
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.546
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.545
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.540
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.539
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.538
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.537
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.536
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.535
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.534
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.533
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.