← Home

@flowlib/nestjs

npm Repository Homepage

A NestJS module for executing Flowlib workflows with batch processing capabilities

8
Versions
MIT
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

robase-gh

Keywords

aianthropicbatch-processingflowlibnestjsopenaiworkflow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is consistent with SLSA-attested CI/CD pipeline; stable pattern for this package. ai
phantom-deps phantom-dep:@flowlib/action-kit AI (phantom-deps): Same-org dep; same rationale as @flowlib/db. ai
phantom-deps phantom-dep:@flowlib/db AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:rxjs AI (phantom-deps): rxjs is a standard NestJS peer dependency; declared but not directly imported is expected for NestJS modules. ai
phantom-deps phantom-dep:@nestjs/core AI (phantom-deps): NestJS core is a peer dep; not directly imported in module packages is standard pattern. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): reflect-metadata is a known implicit runtime dep for NestJS/TypeScript decorators; not directly imported is expected. ai

Versions (showing 8 of 8)

Version Deps Published
0.0.8 8 / 12
0.0.7 8 / 12
0.0.6 8 / 12
0.0.5 7 / 12
0.0.4 5 / 12
0.0.3 5 / 12
0.0.2 5 / 12
0.0.1 5 / 12

v0.0.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.6

2 findings
HIGH Publisher changed: robase-gh → GitHub Actions (on 2026-05-05) provenance

This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

2 findings
HIGH Publisher changed: robase-gh → GitHub Actions (on 2026-05-03) provenance

This version was published by a different npm account than previous versions on 2026-05-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.1

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.