lognow
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/standalone/index.js | AI (source-diff): Minified standalone bundle for jsdelivr/unpkg; expected pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/electron/main/index.mjs | AI (source-diff): Rolldown bundler output; long lines are minified but readable ESM, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/node/index.mjs | AI (source-diff): Same rolldown bundle pattern; stable false positive for this build toolchain. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a legitimate runtime dep for type-only usage in this package's context. | ai | |
| provenance | no-provenance | AI (provenance): Package has no provenance but is otherwise clean; stable false-positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 16 / 12 | |
| 0.6.1 | 16 / 11 | |
| 0.6.0 | 16 / 11 | |
| 0.5.2 | 16 / 10 | |
| 0.5.1 | 16 / 9 | |
| 0.5.0 | 15 / 10 | |
| 0.4.1 | 2 / 21 | |
| 0.4.0 | 2 / 21 | |
| 0.3.2 | 2 / 21 | |
| 0.3.1 | 2 / 21 | |
| 0.3.0 | 2 / 21 | |
| 0.2.2 | 2 / 20 | |
| 0.2.1 | 2 / 20 | |
| 0.2.0 | 1 / 21 | |
| 0.1.0 | 1 / 18 |
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.