@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, so a manually published version cannot be tied back to a reviewed commit.
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 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.6.54 | 14 / 6 | |
| 0.6.53 | 14 / 6 | |
| 0.6.46 | 14 / 6 | |
| 0.6.43 | 14 / 6 | |
| 0.6.42 | 14 / 6 | |
| 0.6.41 | 14 / 6 | |
| 0.6.40 | 11 / 6 | |
| 0.6.39 | 11 / 6 | |
| 0.6.38 | 11 / 6 | |
| 0.6.37 | 11 / 6 | |
| 0.6.36 | 11 / 6 | |
| 0.6.35 | 11 / 6 | |
| 0.6.34 | 11 / 3 | |
| 0.6.33 | 11 / 3 | |
| 0.6.32 | 11 / 3 | |
| 0.6.31 | 11 / 3 | |
| 0.6.30 | 11 / 3 | |
| 0.6.29 | 11 / 3 | |
| 0.6.28 | 11 / 3 | |
| 0.6.27 | 11 / 3 | |
| 0.6.26 | 11 / 3 | |
| 0.6.25 | 11 / 3 | |
| 0.6.24 | 11 / 3 | |
| 0.6.23 | 11 / 3 | |
| 0.6.22 | 11 / 3 | |
| 0.6.21 | 11 / 3 | |
| 0.6.20 | 11 / 3 | |
| 0.6.19 | 11 / 3 | |
| 0.6.18 | 11 / 3 | |
| 0.6.17 | 11 / 3 | |
| 0.6.16 | 11 / 3 | |
| 0.6.15 | 11 / 3 |
v0.6.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.