@emuanalytics/flow-rdf-ui
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 10 of 10)
| 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 | |
| 4.1.22 | 15 / 66 | |
| 4.1.21 | 15 / 66 | |
| 4.1.20 | 15 / 66 | |
| 4.1.19 | 15 / 66 | |
| 4.1.18 | 15 / 66 |
v4.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.