← Home

@voiceflow/logger

npm

A standardized package for logging built on `pino`.

15
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pmvrmcamandasteinhauerandrewlawrencetylerhhaneffervescentiajosh_vfvoiceflow-gallaganz4o4zsssoflyyyxavidopzhilightytolunsanasarjanjughazyandandonovan78theprofabuyakninabondarpixelzarrohan-mandhotra-vfose-voiceflowbreamjbydeleyvf-serviceaccountchidi-voiceflowpateriackdevinabaghmar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Service-account publisher with strong track record; roster churn expected in monorepo. ai
maintainer-change maintainer-removed AI (maintainer-change): Same org roster sync, no behavior change in diff. ai
phantom-deps phantom-dep:pino-pretty AI (phantom-deps): Standard pino transport config reference, not a real import gap. ai

Versions (showing 15 of 15)

Version Deps Published
2.8.0 5 / 2
2.7.1 5 / 2
2.7.0 5 / 2
2.6.1 6 / 1
2.6.0 6 / 1
2.5.0 6 / 1
2.4.4 6 / 1
2.4.1 6 / 1
2.4.0 6 / 1
2.3.2 6 / 28
2.3.1 6 / 28
2.3.0 6 / 28
2.2.0 6 / 27
2.1.0 6 / 27
2.0.0 6 / 27

v2.4.1

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.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.

v2.3.0

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.

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

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.

v2.0.0

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.