@copass/datasource-olane
Olane OS data source driver for Copass — start/stop/status of local Olane OS instances, address book, worlds, and identity management
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom detection likely misses ESM/build-time usage patterns in this package. | ai | |
| phantom-deps | phantom-dep:@olane/o-storage | AI (phantom-deps): Same-org dep; phantom detection likely misses indirect/config-level usage in this ESM package. | ai | |
| phantom-deps | phantom-dep:@olane/o-node | AI (phantom-deps): Declared dep referenced in config files, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@olane/o-client | AI (phantom-deps): Declared dep referenced in config files, not direct imports; stable pattern for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 8 / 5 | |
| 0.6.2 | 8 / 5 | |
| 0.6.1 | 8 / 5 | |
| 0.6.0 | 8 / 5 | |
| 0.5.7 | 8 / 5 | |
| 0.5.6 | 8 / 5 | |
| 0.5.5 | 7 / 5 | |
| 0.5.4 | 7 / 5 | |
| 0.5.3 | 6 / 5 | |
| 0.5.2 | 6 / 5 | |
| 0.5.1 | 6 / 5 | |
| 0.5.0 | 6 / 5 | |
| 0.4.1 | 6 / 5 | |
| 0.3.8 | 6 / 5 | |
| 0.3.7 | 6 / 5 | |
| 0.3.6 | 6 / 5 | |
| 0.3.5 | 6 / 5 | |
| 0.3.4 | 6 / 5 | |
| 0.3.0 | 6 / 5 | |
| 0.2.6 | 6 / 5 | |
| 0.2.4 | 6 / 5 | |
| 0.2.3 | 6 / 5 | |
| 0.2.2 | 6 / 5 | |
| 0.2.1 | 6 / 5 | |
| 0.1.1 | 6 / 5 |
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
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.