← Home

@meistrari/logger

npm

@meistrari/logger

10
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

0xthierryrjmunhozamorim33henrykunhrodrigo_lgczaghiianfiremanmatheusvellonethullyocunharenanllm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env spread feeds a Zod schema that extracts only specific named vars; standard config-validation pattern, not exfiltration. ai

Versions (showing 10 of 10)

Version Deps Published
2.1.8 2 / 7
2.1.7 2 / 4
2.1.6 2 / 4
2.1.5 2 / 4
2.1.1 2 / 3
2.1.0 2 / 3
2.0.3 2 / 3
2.0.2 2 / 3
2.0.1 2 / 3
2.0.0 2 / 3

v2.1.7

1 finding
LOW No provenance attestation provenance

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

v2.1.6

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.1.5

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

2 findings
HIGH env-spread: src/logger.ts:12 semgrep

Spreading entire process.env into an object — may capture all secrets 10 | ENVIRONMENT: z.enum(['unknown', 'development', 'preview', 'staging', 'forninho', 'production']).default('unknown'), 11 | SERVICE_VERSION: z.string().default('unknown'), > 12 | }).parse({ 13 | ...process.env, 14 | // Support both ENVIRONMENT and NODE_ENV as inputs

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.2

2 findings
HIGH env-spread: src/logger.ts:12 semgrep

Spreading entire process.env into an object — may capture all secrets 10 | ENVIRONMENT: z.enum(['unknown', 'development', 'preview', 'staging', 'forninho', 'production']).default('unknown'), 11 | SERVICE_VERSION: z.string().default('unknown'), > 12 | }).parse({ 13 | ...process.env, 14 | // Support both ENVIRONMENT and NODE_ENV as inputs

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.1

2 findings
HIGH env-spread: src/logger.ts:12 semgrep

Spreading entire process.env into an object — may capture all secrets 10 | ENVIRONMENT: z.enum(['unknown', 'development', 'preview', 'staging', 'forninho', 'production']).default('unknown'), 11 | SERVICE_VERSION: z.string().default('unknown'), > 12 | }).parse({ 13 | ...process.env, 14 | // Support both ENVIRONMENT and NODE_ENV as inputs

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

2 findings
HIGH env-spread: src/logger.ts:12 semgrep

Spreading entire process.env into an object — may capture all secrets 10 | ENVIRONMENT: z.enum(['unknown', 'development', 'staging', 'forninho', 'production']).default('unknown'), 11 | SERVICE_VERSION: z.string().default('unknown'), > 12 | }).parse({ 13 | ...process.env, 14 | // Support both ENVIRONMENT and NODE_ENV as inputs

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.