← Home

@emuanalytics/flow-rdf-ui

npm
5
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

robin.summerhillmark.brundell

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal scoped package; missing description/repo/keywords is consistent with private org library pattern across all versions. ai
npm-metadata no-description AI (npm-metadata): Internal org package; no description is stable pattern across all 151 versions. ai
phantom-deps phantom-dep:deep-equal AI (phantom-deps): Same pattern — bundled ESM library with indirect dep usage. ai
phantom-deps phantom-dep:debug AI (phantom-deps): Declared runtime dep in a bundled ESM package; indirect usage via bundler is expected. ai
phantom-deps phantom-dep:chartjs-adapter-dayjs-4 AI (phantom-deps): Same pattern — bundled ESM library with indirect dep usage. ai
phantom-deps phantom-dep:@lit-labs/motion AI (phantom-deps): Same pattern — bundled ESM library with indirect dep usage. ai
phantom-deps phantom-dep:deepmerge AI (phantom-deps): Same pattern — bundled ESM library with indirect dep usage. ai

Versions (showing 5 of 5)

Version Deps Published
4.1.27 15 / 66
4.1.26 15 / 66
4.1.25 15 / 66
4.1.24 15 / 66
4.1.23 15 / 66

v4.1.27

1 finding
LOW No provenance attestation provenance

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

v4.1.26

1 finding
LOW No provenance attestation provenance

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

v4.1.25

1 finding
LOW No provenance attestation provenance

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

v4.1.23

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.