node-opcua-crypto
Crypto tools for Node-OPCUA
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 | obfuscated-file:dist/source/index_web.cjs | AI (source-diff): Standard tsup CJS bundle output; long lines are minified build artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Standard tsup CJS bundle output; long lines are minified build artifacts, not obfuscation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; dormancy is not a concern here. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is used in npm scripts; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/sshpk | AI (phantom-deps): @types packages loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/jsrsasign | AI (phantom-deps): @types packages loaded by convention; stable false positive. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.3.6 | 4 / 11 | |
| 5.3.5 | 4 / 11 | |
| 5.3.4 | 4 / 11 | |
| 5.3.3 | 4 / 11 | |
| 5.3.2 | 3 / 11 | |
| 5.3.1 | 3 / 11 | |
| 5.3.0 | 3 / 11 | |
| 5.2.0 | 3 / 11 | |
| 5.1.0 | 3 / 3 | |
| 5.0.0 | 8 / 2 | |
| 4.17.0 | 8 / 2 | |
| 4.16.1 | 9 / 2 |
v5.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.