← Home

@boringnode/encryption

npm
8
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

julien-r44romainlanzvirk

Keywords

encryptioncrypto

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): virk is a listed contributor and AdonisJS ecosystem maintainer; transition from romainlanz is consistent with the project's org structure. ai
maintainer-change maintainer-added AI (maintainer-change): virk is a named contributor in package.json; addition is expected for this AdonisJS-ecosystem package. ai
phantom-deps phantom-dep:@poppinss/utils AI (phantom-deps): @poppinss/utils is a declared runtime dependency used by the AdonisJS ecosystem; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.0 1 / 16
0.2.5 1 / 16
0.2.4 1 / 16
0.2.3 1 / 16
0.2.2 1 / 16
0.2.1 1 / 16
0.2.0 1 / 16
0.1.0 1 / 16

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

2 findings
HIGH Publisher changed: romainlanz → virk (on 2026-01-07) provenance

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

LOW No provenance attestation provenance

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

v0.2.3

2 findings
HIGH Publisher changed: romainlanz → virk (on 2026-01-07) provenance

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

LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

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

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.