@ox-jsdoc/decoder
Lazy JS decoder for the ox-jsdoc Binary AST format. Shared by NAPI and WASM bindings.
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used solely to create a debug class with a dynamic name for V8 inspector; input is internal typeName, not external data. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.16 | 0 / 1 | |
| 0.0.15 | 0 / 1 | |
| 0.0.14 | 0 / 1 | |
| 0.0.12 | 0 / 1 | |
| 0.0.10 | 0 / 1 | |
| 0.0.9 | 0 / 1 | |
| 0.0.8 | 0 / 1 | |
| 0.0.7 | 0 / 1 | |
| 0.0.6 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.4 | 0 / 1 | |
| 0.0.3 | 0 / 1 |
v0.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.