node-addon-api
Node.js API (Node-API)
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from nodejs-foundation to GitHub Actions CI/CD publishing with SLSA provenance; legitimate automation migration for the nodejs org. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process in tools/check-napi.js is a build-time utility for checking N-API compatibility; not run at install time. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable package under nodejs org; infrequent releases are normal for a stable API surface. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 8.8.0 | 0 / 8 | |
| 8.7.0 | 0 / 8 | |
| 8.6.0 | 0 / 8 | |
| 8.5.0 | 0 / 8 | |
| 8.4.0 | 0 / 8 | |
| 8.3.1 | 0 / 8 | |
| 8.3.0 | 0 / 8 | |
| 8.2.2 | 0 / 14 | |
| 8.2.1 | 0 / 14 | |
| 8.2.0 | 0 / 14 | |
| 8.1.0 | 0 / 14 | |
| 8.0.0 | 0 / 13 | |
| 7.1.1 | 0 / 13 | |
| 7.1.0 | 0 / 13 | |
| 7.0.0 | 0 / 13 | |
| 6.1.0 | 0 / 13 | |
| 6.0.0 | 0 / 13 | |
| 5.1.0 | 0 / 13 | |
| 5.0.0 | 0 / 13 | |
| 4.3.0 | 0 / 13 | |
| 4.2.0 | 0 / 7 | |
| 4.1.0 | 0 / 6 | |
| 4.0.0 | 0 / 6 | |
| 3.2.1 | 0 / 6 | |
| 3.2.0 | 0 / 6 | |
| 3.1.0 | 0 / 6 | |
| 3.0.2 | 0 / 4 | |
| 3.0.1 | 0 / 2 | |
| 3.0.0 | 0 / 2 | |
| 2.0.2 | 0 / 1 | |
| 2.0.1 | 0 / 1 | |
| 2.0.0 | 0 / 1 | |
| 1.7.2 | 0 / 1 | |
| 1.7.1 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.6.3 | 0 / 1 | |
| 1.6.2 | 0 / 1 | |
| 1.6.1 | 0 / 1 | |
| 1.6.0 | 0 / 1 | |
| 1.5.0 | 0 / 1 | |
| 1.4.0 | 0 / 1 | |
| 1.3.0 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 | |
| 0.6.3 | 0 / 1 | |
| 0.6.2 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.5 | 0 / 0 | |
| 0.3.4 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 1 | |
| 0.1.0 | 0 / 1 |
v8.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-09-30. This could indicate a legitimate maintainer transition or an account compromise.
v8.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-07-08. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-07-12. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-01-19. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-15. This could indicate a legitimate maintainer transition or an account compromise.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.