@awell-health/extensions-core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:rate-limiter-flexible | AI (dependencies): rate-limiter-flexible is a well-known npm library for rate limiting; its use in this core extensions library is legitimate and expected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect cosmetic metadata gaps typical of an internal org library, not spam/malware indicators. Package has 116 versions and 1062 days of history. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): TypeScript type package declared as runtime dep; framework-scoped convention, not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): TypeScript type package declared as runtime dep; framework-scoped convention, not a security concern. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.1.15 | 11 / 24 | |
| 1.1.14 | 11 / 24 | |
| 1.1.13 | 11 / 24 | |
| 1.1.12 | 11 / 24 | |
| 1.1.11 | 11 / 24 | |
| 1.1.10 | 11 / 24 | |
| 1.1.9 | 11 / 24 | |
| 1.1.8 | 11 / 24 | |
| 1.1.7 | 11 / 24 | |
| 1.1.6 | 11 / 24 | |
| 1.1.5 | 11 / 24 | |
| 1.1.4 | 11 / 24 | |
| 1.1.3 | 11 / 24 | |
| 1.1.2 | 11 / 24 | |
| 1.1.1 | 11 / 24 | |
| 1.1.0 | 11 / 24 | |
| 1.0.28 | 10 / 20 | |
| 1.0.27 | 10 / 20 | |
| 1.0.26 | 10 / 20 |
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.