@goodchat/storage
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:better-auth | AI (phantom-deps): better-auth is legitimately declared and used in schema/auth files; phantom-dep false positive for config-referenced dependencies. | ai | |
| phantom-deps | phantom-dep:@neondatabase/serverless | AI (phantom-deps): @neondatabase/serverless is legitimately declared and referenced in postgres schema; phantom-dep false positive for config-referenced dependencies. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.20 | 8 / 5 | |
| 0.0.19 | 8 / 5 | |
| 0.0.18 | 8 / 5 | |
| 0.0.17 | 8 / 5 | |
| 0.0.16 | 8 / 5 | |
| 0.0.15 | 8 / 5 | |
| 0.0.14 | 8 / 4 | |
| 0.0.13 | 8 / 4 | |
| 0.0.12 | 8 / 4 | |
| 0.0.11 | 8 / 4 |
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.