@osdk/vite-plugin-oac
A Vite plugin that enables **Ontology as Code (OAC)** development by automatically generating ontology assets from TypeScript/JavaScript ontology definitions. This plugin handles the complete pipeline from ontology source code to ready-to-use OSDK (Ontolo
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Palantir org migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this monorepo. | ai | |
| phantom-deps | phantom-dep:@osdk/api | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/cli | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/maker | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:@osdk/client.unstable | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for @osdk/* packages. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dependency used by the vite plugin server; phantom-dep false positive. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 13 / 4 | |
| 0.26.0 | 13 / 4 | |
| 0.25.0 | 13 / 4 | |
| 0.24.0 | 13 / 4 | |
| 0.23.0 | 13 / 4 | |
| 0.22.0 | 13 / 4 | |
| 0.21.0 | 13 / 4 | |
| 0.20.0 | 13 / 4 | |
| 0.19.0 | 13 / 4 | |
| 0.18.0 | 13 / 4 | |
| 0.17.0 | 13 / 4 | |
| 0.15.0 | 13 / 4 | |
| 0.14.0 | 13 / 4 | |
| 0.13.0 | 13 / 4 | |
| 0.12.0 | 13 / 4 | |
| 0.11.0 | 13 / 4 | |
| 0.10.0 | 13 / 4 | |
| 0.9.0 | 13 / 4 | |
| 0.8.0 | 13 / 4 | |
| 0.7.0 | 13 / 4 | |
| 0.6.0 | 13 / 4 | |
| 0.5.9 | 13 / 4 | |
| 0.5.8 | 13 / 4 | |
| 0.5.7 | 13 / 4 | |
| 0.5.6 | 13 / 4 | |
| 0.5.5 | 13 / 4 | |
| 0.5.4 | 13 / 4 | |
| 0.5.3 | 13 / 4 | |
| 0.5.2 | 13 / 4 | |
| 0.5.1 | 13 / 4 | |
| 0.5.0 | 13 / 4 | |
| 0.4.3 | 13 / 4 | |
| 0.4.2 | 13 / 4 | |
| 0.4.1 | 13 / 4 | |
| 0.4.0 | 13 / 4 | |
| 0.3.7 | 13 / 4 | |
| 0.3.6 | 13 / 4 | |
| 0.3.5 | 13 / 4 | |
| 0.3.4 | 13 / 4 | |
| 0.3.3 | 13 / 4 | |
| 0.3.2 | 13 / 4 | |
| 0.3.1 | 13 / 4 | |
| 0.3.0 | 13 / 4 | |
| 0.2.2 | 13 / 4 | |
| 0.2.1 | 13 / 4 | |
| 0.2.0 | 13 / 4 | |
| 0.1.4 | 13 / 4 | |
| 0.1.3 | 13 / 4 | |
| 0.1.2 | 13 / 4 | |
| 0.1.1 | 13 / 4 | |
| 0.1.0 | 13 / 4 |
v0.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.