@beauraines/sprint-tracker
Database and R visualizations to track sprint performance
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool using child_process in a stats command; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:sqlite | AI (phantom-deps): Optional backend dependency loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@azure/cosmos | AI (phantom-deps): Framework-scoped Azure backend; loaded by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:azure-storage | AI (phantom-deps): Optional Azure storage backend; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:should-release | AI (phantom-deps): Dev/release tooling dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:standard-version | AI (phantom-deps): Dev/release tooling dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@azure/data-tables | AI (phantom-deps): Optional Azure backend; loaded by convention, stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.6.54 | 14 / 6 | |
| 0.6.53 | 14 / 6 | |
| 0.6.46 | 14 / 6 | |
| 0.6.43 | 14 / 6 |
v0.6.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.