@niivue/niivue
minimal webgl2 nifti image viewer
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Bundled build output growth from adding legitimate deps, not injected payload. | ai | |
| dependencies | unvetted-dep:daikon | AI (dependencies): daikon is a DICOM parsing lib appropriate for a medical image viewer. | ai | |
| source-diff | obfuscated-file:build/index.js | AI (source-diff): tsup/esbuild bundled output, not obfuscation; standard build helper preamble. | ai | |
| source-diff | encoded-string-file:dist/niivue.umd.js | AI (source-diff): Same WASM base64 blob in UMD build; stable false positive for this package. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Encoded strings are WebAssembly binary blobs (blosc codec) embedded as base64 — standard WASM bundling pattern for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP appears only in a JSDoc comment pointing to a local dev server demo URL, not in runtime code. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding used for legitimate mesh file format parsing (gzip-compressed binary data in NVMesh loaders). | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.69.0 | 7 / 27 | |
| 0.68.2 | 7 / 27 | |
| 0.68.1 | 7 / 27 | |
| 0.68.0 | 7 / 27 | |
| 0.67.0 | 7 / 27 | |
| 0.66.0 | 7 / 26 | |
| 0.65.0 | 7 / 26 | |
| 0.42.0 | 8 / 29 | |
| 0.41.1 | 8 / 30 | |
| 0.41.0 | 8 / 31 | |
| 0.40.0 | 8 / 31 | |
| 0.10.1 | 0 / 13 | |
| 0.10.0 | 0 / 13 | |
| 0.9.3 | 0 / 13 | |
| 0.9.2 | 0 / 13 | |
| 0.9.1 | 0 / 13 | |
| 0.9.0 | 0 / 13 | |
| 0.8.3 | 0 / 13 | |
| 0.8.2 | 0 / 13 | |
| 0.8.1 | 0 / 13 | |
| 0.7.0 | 0 / 13 | |
| 0.6.0 | 0 / 13 | |
| 0.5.1 | 0 / 13 | |
| 0.3.0 | 0 / 13 | |
| 0.2.4 | 0 / 13 | |
| 0.2.2 | 0 / 12 | |
| 0.2.1 | 0 / 12 | |
| 0.2.0 | 0 / 12 | |
| 0.1.2 | 0 / 6 | |
| 0.1.1 | 0 / 6 | |
| 0.1.0 | 0 / 6 | |
| 0.0.1 | 0 / 7 |
v0.68.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (thanayik) on 2026-02-25, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.68.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (thanayik) on 2026-02-21, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
2 findingsNewly 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.41.1
2 findingsNewly 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.41.0
2 findingsNewly 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.40.0
2 findingsNewly 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.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.