← Home

@nextdog/next

npm Repository Homepage

Next.js plugin for NextDog — zero-config dev observability

11
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

cscherban

Keywords

nextjsobservabilitytracingopentelemetrydevtoolsinstrumentation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:nuxt AI (typosquat): @nextdog/next is a Next.js observability plugin, not a nuxt typosquat; scoped name reflects the NextDog project. ai
typosquat typosquat.levenshtein:jest AI (typosquat): 2-edit distance to jest is coincidental; package is clearly a Next.js instrumentation plugin. ai
typosquat typosquat.levenshtein:knex AI (typosquat): 2-edit distance to knex is coincidental; unrelated domain (observability vs. SQL). ai
phantom-deps phantom-dep:@nextdog/core AI (phantom-deps): Same-org sibling dep; may be re-exported rather than directly imported in analyzed files. ai
phantom-deps phantom-dep:@opentelemetry/api AI (phantom-deps): Referenced in config/instrumentation files; stable false positive for OTel-based packages. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.0 6 / 3
0.4.0 6 / 3
0.3.2 5 / 3
0.3.1 5 / 3
0.3.0 5 / 3
0.2.1 5 / 3
0.2.0 5 / 3
0.1.3 5 / 3
0.1.2 5 / 3
0.1.1 5 / 3
0.1.0 5 / 3

v1.0.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@nextdog/next' is 1 edit(s) away from popular package 'nuxt'.

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

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

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

v0.1.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@nextdog/next' is 1 edit(s) away from popular package 'nuxt'.

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.