@alveole/core
Core for Alveole.
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:@uiw/react-signature | AI (phantom-deps): Platform/peer dep pattern in a monorepo; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:react-native-signature-canvas | AI (phantom-deps): Platform-specific binary package; phantom-dep false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private monorepo core package; sparse README/metadata and empty dist entry are expected for internal packages. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @alveole/core package; not a typosquat of cors — the org name makes the intent clear. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.38.0 | 2 / 3 | |
| 0.37.3 | 2 / 3 | |
| 0.37.2 | 2 / 3 | |
| 0.36.2 | 0 / 3 | |
| 0.36.1 | 0 / 3 | |
| 0.36.0 | 0 / 3 | |
| 0.35.3 | 0 / 2 | |
| 0.35.2 | 0 / 2 | |
| 0.35.1 | 0 / 2 | |
| 0.35.0 | 0 / 2 | |
| 0.34.9 | 0 / 2 | |
| 0.34.8 | 0 / 2 | |
| 0.34.7 | 0 / 2 | |
| 0.34.6 | 0 / 2 |
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.