@octavus/docs
Documentation content for Octavus SDKs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/search.mjs | AI (source-diff): Long lines are a bundled MiniSearch index with inline JSON doc content; not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @octavus/docs package is unrelated to cors; Levenshtein match is coincidental. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 1 / 5 | |
| 6.0.0 | 1 / 5 | |
| 5.1.0 | 1 / 5 | |
| 5.0.0 | 1 / 5 | |
| 4.2.0 | 1 / 5 | |
| 4.1.0 | 1 / 5 | |
| 4.0.0 | 1 / 5 | |
| 3.7.0 | 1 / 5 | |
| 3.6.0 | 1 / 5 | |
| 3.5.0 | 1 / 5 | |
| 3.4.0 | 1 / 5 | |
| 3.3.0 | 1 / 5 | |
| 3.2.0 | 1 / 5 | |
| 3.1.0 | 1 / 5 | |
| 3.0.0 | 1 / 5 | |
| 2.21.0 | 1 / 5 | |
| 2.20.0 | 1 / 5 | |
| 2.19.0 | 1 / 5 | |
| 2.18.0 | 1 / 5 | |
| 2.17.0 | 1 / 5 | |
| 2.16.0 | 1 / 5 | |
| 2.15.0 | 1 / 5 | |
| 2.14.0 | 1 / 5 | |
| 2.13.0 | 1 / 5 | |
| 2.12.0 | 1 / 5 | |
| 2.11.0 | 1 / 5 | |
| 2.10.0 | 1 / 5 | |
| 2.9.0 | 1 / 5 | |
| 2.8.0 | 1 / 5 | |
| 2.7.0 | 1 / 5 | |
| 2.6.0 | 1 / 5 | |
| 2.5.0 | 1 / 5 | |
| 2.4.0 | 1 / 5 | |
| 2.3.0 | 1 / 5 | |
| 2.2.0 | 1 / 5 | |
| 2.1.0 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.0.0 | 1 / 5 | |
| 0.0.9 | 1 / 5 | |
| 0.0.8 | 1 / 5 | |
| 0.0.7 | 1 / 5 | |
| 0.0.6 | 1 / 5 | |
| 0.0.5 | 1 / 5 | |
| 0.0.4 | 1 / 5 | |
| 0.0.3 | 1 / 5 | |
| 0.0.2 | 1 / 5 | |
| 0.0.1 | 1 / 5 |
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
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.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.