@nextdog/next
Next.js plugin for NextDog — zero-config dev observability
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.1.8 | 6 / 3 | |
| 1.1.7 | 6 / 3 | |
| 1.1.6 | 6 / 3 | |
| 1.1.5 | 6 / 3 | |
| 1.1.4 | 6 / 3 | |
| 1.1.3 | 6 / 3 | |
| 1.1.2 | 6 / 3 | |
| 1.1.1 | 6 / 3 | |
| 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.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.