@or-sdk/agents
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:lodash | AI (phantom-deps): Directly imported in source; types in devDeps. Stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash.camelcase | AI (phantom-deps): Directly imported in source; types in devDeps. Stable false positive. | ai | |
| phantom-deps | phantom-dep:graphql-tag | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:dedent | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/schema | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/merge | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this SDK package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.20.2 | 9 / 3 | |
| 4.20.1 | 9 / 3 | |
| 4.20.0 | 9 / 3 | |
| 4.19.0 | 9 / 3 | |
| 4.18.2 | 9 / 3 | |
| 4.18.1 | 9 / 3 | |
| 4.18.0 | 9 / 3 | |
| 4.17.0 | 9 / 3 | |
| 4.16.0 | 9 / 3 | |
| 4.15.1 | 8 / 3 | |
| 4.15.0 | 8 / 3 | |
| 4.14.0 | 8 / 3 | |
| 4.13.0 | 8 / 3 | |
| 4.12.5 | 8 / 3 | |
| 4.12.4 | 8 / 3 | |
| 4.12.3 | 8 / 4 | |
| 4.12.2 | 8 / 4 | |
| 4.12.1 | 8 / 4 | |
| 4.12.0 | 8 / 4 | |
| 4.11.3 | 8 / 4 | |
| 4.11.2 | 8 / 4 | |
| 4.11.1 | 8 / 4 | |
| 4.11.0 | 8 / 4 | |
| 4.10.1 | 8 / 4 | |
| 4.10.0 | 8 / 4 | |
| 4.9.1 | 10 / 7 |
v4.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.