@or-sdk/idw
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@or-sdk/deployer | AI (phantom-deps): Same-org scoped package; likely transitive or internal monorepo dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established internal SDK package; metadata gaps typical of monorepo/internal packages, not spam. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.0.2 | 2 / 2 | |
| 9.0.1 | 2 / 2 | |
| 9.0.0 | 2 / 2 | |
| 8.2.2 | 3 / 2 | |
| 8.2.1 | 3 / 2 | |
| 8.2.0 | 3 / 2 | |
| 8.1.1 | 3 / 2 | |
| 8.1.0 | 3 / 2 | |
| 8.0.0 | 3 / 2 | |
| 7.22.0 | 3 / 2 | |
| 7.21.4 | 3 / 2 | |
| 7.21.3 | 3 / 2 | |
| 7.21.2 | 3 / 2 | |
| 7.21.1 | 3 / 2 |
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.