@oiyo/core
oiyo 是以融合AI协作,提升开发体验,降低心智成本为三大理念的 UniApp 增强型工程框架
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:enhanced-resolve | AI (phantom-deps): Bundled into dist output; not directly imported at source level but legitimately used. | ai | |
| phantom-deps | phantom-dep:c12 | AI (phantom-deps): Config-loading utility; loaded by convention, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vue/compiler-sfc | AI (phantom-deps): Framework-scoped package loaded by convention in Vue tooling; stable false positive. | ai | |
| phantom-deps | phantom-dep:pathe | AI (phantom-deps): Loaded by convention in build tooling context; stable false positive. | ai | |
| phantom-deps | phantom-dep:tinyglobby | AI (phantom-deps): Loaded by convention in build tooling context; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Vue/Vite plugin package; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): Framework-scoped package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/parser | AI (phantom-deps): Framework-scoped package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:defu | AI (phantom-deps): Build-tool dep loaded via c12/config convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ansis | AI (phantom-deps): Loaded by convention in build tooling context; stable false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 15 / 3 | |
| 0.3.6 | 14 / 3 | |
| 0.3.5 | 14 / 3 | |
| 0.3.4 | 14 / 3 | |
| 0.3.3 | 14 / 3 | |
| 0.3.2 | 14 / 3 | |
| 0.3.1 | 14 / 3 | |
| 0.3.0 | 11 / 5 | |
| 0.2.1 | 10 / 3 | |
| 0.2.0 | 10 / 3 | |
| 0.1.2 | 11 / 2 | |
| 0.1.1 | 11 / 2 | |
| 0.1.0 | 11 / 2 | |
| 0.0.4 | 11 / 2 | |
| 0.0.3 | 11 / 2 | |
| 0.0.1 | 10 / 2 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
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.2
2 findingsPackage name '@oiyo/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage name '@oiyo/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage name '@oiyo/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
2 findingsPackage name '@oiyo/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findingsPackage name '@oiyo/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsPackage name '@oiyo/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.