satteri
High-performance Markdown and MDX processing
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): napi-rs native binding; .node file is the expected platform binary artifact for this package type. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('ldd --version') is standard napi-rs musl detection; fixed command, no user input. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): napi-rs NAPI_RS_NATIVE_LIBRARY_PATH override; documented escape hatch for native bindings. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetches the .wasm binary in the browser WASI entrypoint; expected for WASM binding packages. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): napi-rs musl detection pattern; stable for this native binding package. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): Type-only dependency used by convention in TypeScript ecosystem; not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/unist | AI (phantom-deps): Type-only dependency used by convention in TypeScript ecosystem; not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): Type-only dependency used by convention in TypeScript ecosystem; not directly imported. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 4 / 26 | |
| 0.6.2 | 3 / 26 | |
| 0.6.1 | 3 / 26 | |
| 0.6.0 | 3 / 26 | |
| 0.3.5 | 3 / 26 | |
| 0.3.0 | 3 / 25 | |
| 0.2.8 | 3 / 25 | |
| 0.2.2 | 3 / 7 | |
| 0.2.1 | 3 / 7 | |
| 0.2.0 | 3 / 7 | |
| 0.1.3 | 3 / 6 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 6 / 5 |
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • satteri_napi.linux-x64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • satteri_napi.linux-x64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.