@logtail/node
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:zod | AI (typosquat): Levenshtein match is spurious; @logtail/node is a scoped logging package with no relation to zod. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): minimatch is a declared runtime dep used in config/glob matching; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@types/stack-trace | AI (phantom-deps): Type-only package loaded by convention; phantom-dep false positive for @types/* packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.5.8 | 6 / 3 | |
| 0.5.6 | 6 / 3 | |
| 0.5.5 | 6 / 3 | |
| 0.5.4 | 6 / 3 | |
| 0.5.3 | 8 / 3 | |
| 0.5.2 | 8 / 3 | |
| 0.5.0 | 8 / 3 |
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.