@emuanalytics/flow-pipelines
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@stomp/tcp-wrapper | AI (dependencies): Companion package to @stomp/stompjs for TCP transport; fits the package's messaging pipeline context. | ai | |
| dependencies | unvetted-dep:pg-custom-types | AI (dependencies): Legitimate PostgreSQL type extension; stable dependency across many versions of this package. | ai | |
| dependencies | unvetted-dep:pg-postgis-types | AI (dependencies): Legitimate PostGIS type extension; stable dependency across many versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established internal package; lack of provenance is consistent across all 59 versions and is not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:pg-custom-types | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:logform | AI (phantom-deps): logform is a declared runtime dep used transitively via winston; phantom-dep heuristic false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): 59 versions over 1005 days; scoped org package with no repo link is common for internal tooling. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is consistent across its version history. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 30 / 23 | |
| 1.1.1 | 27 / 25 | |
| 1.1.0 | 27 / 25 | |
| 1.0.11 | 27 / 25 | |
| 1.0.10 | 27 / 24 | |
| 1.0.9 | 27 / 24 | |
| 1.0.8 | 27 / 24 | |
| 1.0.7 | 27 / 24 | |
| 1.0.6 | 27 / 24 | |
| 1.0.5 | 27 / 24 | |
| 1.0.4 | 27 / 24 | |
| 1.0.3 | 27 / 24 | |
| 1.0.2 | 27 / 24 | |
| 1.0.1 | 27 / 24 | |
| 1.0.0 | 27 / 24 |
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.