@osdk/foundry-sdk-generator
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@osdk/shared.net.errors | AI (phantom-deps): Same-org monorepo peer dep pattern; stable for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/client.api | AI (phantom-deps): Same-org monorepo peer dep pattern; stable for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/shared.net | AI (phantom-deps): Same-org monorepo peer dep pattern; stable for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/shared.client | AI (phantom-deps): Same-org monorepo peer dep pattern; stable for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/shared.net.fetch | AI (phantom-deps): Same-org monorepo peer dep pattern; stable for @osdk/* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Palantir monorepo package; empty description is a consistent pattern across their SDK packages, not a malware indicator. | ai | |
| phantom-deps | phantom-dep:@osdk/api | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@osdk/client | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@osdk/client.unstable | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@osdk/foundry.thirdpartyapplications | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 2.29.0 | 18 / 8 | |
| 2.28.0 | 18 / 8 | |
| 2.27.0 | 18 / 8 | |
| 2.26.0 | 18 / 8 | |
| 2.25.0 | 18 / 8 | |
| 2.24.0 | 18 / 8 | |
| 2.23.0 | 18 / 8 | |
| 2.22.0 | 18 / 8 | |
| 2.21.0 | 18 / 8 | |
| 2.20.0 | 18 / 8 | |
| 2.19.0 | 18 / 8 | |
| 2.17.0 | 18 / 8 | |
| 2.16.0 | 18 / 8 | |
| 2.15.0 | 18 / 8 | |
| 2.14.0 | 18 / 8 | |
| 2.13.0 | 18 / 7 | |
| 2.12.0 | 18 / 7 | |
| 2.11.0 | 18 / 7 | |
| 2.10.0 | 18 / 7 | |
| 2.9.0 | 18 / 7 | |
| 2.8.0 | 18 / 7 | |
| 2.7.8 | 15 / 10 | |
| 2.7.7 | 15 / 10 | |
| 2.7.6 | 15 / 10 | |
| 2.7.5 | 15 / 10 | |
| 2.7.4 | 15 / 10 | |
| 2.7.3 | 15 / 10 | |
| 2.7.2 | 15 / 10 | |
| 2.7.1 | 15 / 10 | |
| 2.7.0 | 15 / 10 | |
| 2.6.3 | 15 / 10 | |
| 2.6.2 | 15 / 10 | |
| 2.6.1 | 15 / 10 | |
| 2.6.0 | 15 / 10 | |
| 2.5.7 | 15 / 10 | |
| 2.5.6 | 15 / 10 | |
| 2.5.5 | 15 / 10 | |
| 2.5.4 | 15 / 10 | |
| 2.5.3 | 15 / 10 | |
| 2.5.2 | 15 / 10 | |
| 2.5.1 | 15 / 10 | |
| 2.5.0 | 15 / 10 | |
| 2.4.2 | 15 / 10 | |
| 2.4.1 | 15 / 10 | |
| 2.4.0 | 15 / 10 | |
| 2.3.4 | 15 / 10 | |
| 2.3.3 | 15 / 10 | |
| 2.3.2 | 15 / 10 | |
| 2.3.1 | 15 / 10 | |
| 2.3.0 | 15 / 10 | |
| 2.2.1 | 15 / 10 |
v2.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.