@opendaw/studio-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/offline-engine.js | AI (source-diff): Minified bundler output, not true obfuscation; part of documented build. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has 181 approved packages without provenance; consistent pattern. | ai | |
| phantom-deps | phantom-dep:@opendaw/nam-wasm | AI (phantom-deps): Same-org dep; likely used indirectly or conditionally within the package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is consistent across all @opendaw/* packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally minimal metadata across the @opendaw monorepo; stable false positive. | ai |
Versions (showing 100 of 131)
| Version | Deps | Published |
|---|---|---|
| 0.1.3 | 16 / 7 | |
| 0.1.2 | 16 / 7 | |
| 0.1.1 | 16 / 7 | |
| 0.1.0 | 16 / 7 | |
| 0.0.156 | 16 / 7 | |
| 0.0.155 | 16 / 7 | |
| 0.0.154 | 16 / 7 | |
| 0.0.153 | 16 / 7 | |
| 0.0.152 | 16 / 7 | |
| 0.0.151 | 16 / 7 | |
| 0.0.150 | 16 / 7 | |
| 0.0.149 | 16 / 7 | |
| 0.0.148 | 16 / 7 | |
| 0.0.147 | 16 / 7 | |
| 0.0.146 | 16 / 7 | |
| 0.0.145 | 16 / 7 | |
| 0.0.144 | 16 / 7 | |
| 0.0.143 | 16 / 7 | |
| 0.0.142 | 16 / 7 | |
| 0.0.141 | 16 / 7 | |
| 0.0.140 | 16 / 7 | |
| 0.0.139 | 16 / 7 | |
| 0.0.138 | 16 / 7 | |
| 0.0.137 | 16 / 7 | |
| 0.0.136 | 16 / 7 | |
| 0.0.135 | 16 / 7 | |
| 0.0.134 | 16 / 7 | |
| 0.0.133 | 16 / 7 | |
| 0.0.132 | 16 / 7 | |
| 0.0.131 | 16 / 7 | |
| 0.0.130 | 15 / 7 | |
| 0.0.129 | 15 / 7 | |
| 0.0.128 | 15 / 7 | |
| 0.0.127 | 15 / 7 | |
| 0.0.126 | 15 / 7 | |
| 0.0.125 | 15 / 7 | |
| 0.0.124 | 15 / 7 | |
| 0.0.123 | 15 / 7 | |
| 0.0.122 | 15 / 7 | |
| 0.0.121 | 15 / 7 | |
| 0.0.120 | 15 / 7 | |
| 0.0.119 | 15 / 7 | |
| 0.0.118 | 15 / 7 | |
| 0.0.117 | 15 / 7 | |
| 0.0.116 | 15 / 7 | |
| 0.0.115 | 15 / 7 | |
| 0.0.114 | 15 / 7 | |
| 0.0.113 | 15 / 7 | |
| 0.0.112 | 15 / 7 | |
| 0.0.111 | 15 / 7 | |
| 0.0.110 | 15 / 7 | |
| 0.0.109 | 15 / 7 | |
| 0.0.108 | 15 / 7 | |
| 0.0.107 | 15 / 7 | |
| 0.0.106 | 15 / 7 | |
| 0.0.105 | 15 / 7 | |
| 0.0.104 | 15 / 7 | |
| 0.0.103 | 15 / 7 | |
| 0.0.102 | 15 / 7 | |
| 0.0.101 | 15 / 7 | |
| 0.0.100 | 15 / 7 | |
| 0.0.99 | 14 / 7 | |
| 0.0.98 | 14 / 7 | |
| 0.0.97 | 14 / 7 | |
| 0.0.96 | 14 / 7 | |
| 0.0.95 | 14 / 7 | |
| 0.0.94 | 14 / 7 | |
| 0.0.93 | 14 / 7 | |
| 0.0.92 | 14 / 7 | |
| 0.0.91 | 14 / 7 | |
| 0.0.90 | 14 / 7 | |
| 0.0.89 | 14 / 7 | |
| 0.0.88 | 14 / 7 | |
| 0.0.87 | 14 / 7 | |
| 0.0.86 | 14 / 7 | |
| 0.0.85 | 14 / 7 | |
| 0.0.84 | 14 / 7 | |
| 0.0.83 | 14 / 7 | |
| 0.0.82 | 14 / 7 | |
| 0.0.81 | 14 / 7 | |
| 0.0.74 | 14 / 7 | |
| 0.0.72 | 14 / 7 | |
| 0.0.71 | 14 / 7 | |
| 0.0.70 | 14 / 7 | |
| 0.0.69 | 14 / 7 | |
| 0.0.67 | 14 / 7 | |
| 0.0.66 | 14 / 7 | |
| 0.0.65 | 14 / 7 | |
| 0.0.63 | 14 / 7 | |
| 0.0.62 | 14 / 7 | |
| 0.0.61 | 14 / 7 | |
| 0.0.60 | 14 / 7 | |
| 0.0.59 | 14 / 7 | |
| 0.0.58 | 14 / 7 | |
| 0.0.57 | 14 / 7 | |
| 0.0.56 | 14 / 7 | |
| 0.0.55 | 14 / 7 | |
| 0.0.54 | 14 / 7 | |
| 0.0.53 | 14 / 7 | |
| 0.0.52 | 14 / 7 |
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.134
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.127
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.126
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.125
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.124
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.123
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.122
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.120
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.119
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.118
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.117
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.114
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.113
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.112
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.111
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.110
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.104
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.