← Home

@b10cks/next

npm Repository Homepage

Next.js integration SDK for b10cks

6
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

badmike

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped @b10cks/next is a Next.js SDK, not a nuxt typosquat. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped package; no relation to jest. ai
typosquat typosquat.levenshtein:knex AI (typosquat): Scoped package; no relation to knex. ai
phantom-deps phantom-dep:@b10cks/richtext AI (phantom-deps): Same-org dep; may be re-exported or used indirectly in build output. ai

Versions (showing 6 of 6)

Version Deps Published
0.3.1 3 / 6
0.3.0 3 / 6
0.2.2 3 / 6
0.2.1 3 / 6
0.2.0 3 / 6
0.1.0 2 / 6

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

v0.2.2

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