← Home

console-browserify

npm Repository Homepage

Emulate console for all the browsers

12
Versions
—
License
Yes
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

ahdinosauranandthakkerashaffer88baluptonbpostlethwaitebretcwmmadefunctzombiedominictarrelnounchemilbayesferossforbeslindesayfpereira1garanngkatsevgoto-bus-stophughskindutnyjmmjprichardsonjryansleichtgewichtlukechildsmafintoshmattdeslmaxogdenmellowmelonparshappkruminsraynossethvincentstevemaosubstacktehshriketerinjokesthlorenzungoldmanyerkopalmayoshuawuytszertosh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs 'npm dedup', a benign housekeeping command. No network access or code execution risk; stable for this package. ai

Versions (showing 12 of 12)

Version Deps Published
1.2.0 0 / 5
1.1.0 1 / 5
1.0.3 0 / 4
1.0.2 0 / 4
1.0.1 0 / 4
0.1.6 0 / 4
0.1.5 0 / 4
0.1.4 1 / 4
0.1.3 1 / 3
0.1.2 1 / 3
0.1.1 1 / 3
0.1.0 1 / 3

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm dedup

LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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