@bemedev/pipe
A utility for creating and managing pipelines in Typescript.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @bemedev/pipe is a pipeline utility; Levenshtein match to 'vite' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped package @bemedev/pipe is a pipeline utility; Levenshtein match to 'pino' is coincidental. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 0 / 18 | |
| 1.6.0 | 0 / 18 | |
| 1.5.5 | 0 / 18 | |
| 1.5.4 | 0 / 18 | |
| 1.5.3 | 0 / 18 | |
| 1.5.2 | 0 / 18 | |
| 1.5.1 | 0 / 18 | |
| 1.5.0 | 0 / 18 | |
| 1.4.0 | 0 / 18 | |
| 1.3.1 | 0 / 18 | |
| 1.3.0 | 0 / 18 | |
| 1.2.0 | 0 / 17 | |
| 1.1.0 | 0 / 17 | |
| 1.0.0 | 0 / 17 | |
| 0.2.0 | 0 / 17 | |
| 0.1.1 | 0 / 18 |
v1.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
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.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.