@kumori/aurora-user-context
user context for the aurora project
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small internal library in early development; lack of provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): jest is a test runner referenced in jest.config.ts; phantom-dep fires because it's in dependencies instead of devDependencies. | ai | |
| phantom-deps | phantom-dep:@jest/globals | AI (phantom-deps): Test framework package loaded by convention; not directly imported in source files. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is referenced in jest.config.ts for test tooling, not a runtime import; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 4 / 6 | |
| 1.0.7 | 4 / 6 | |
| 1.0.6 | 4 / 6 | |
| 1.0.5 | 4 / 6 | |
| 1.0.4 | 4 / 6 | |
| 1.0.3 | 4 / 6 | |
| 1.0.2 | 6 / 4 | |
| 1.0.1 | 6 / 4 | |
| 1.0.0 | 6 / 4 |
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.