@vue-skuilder/courseware
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:paper | AI (phantom-deps): Paper is declared in dependencies and used in the codebase; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo internal package; missing metadata is typical for scoped packages in coordinated releases. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 6 / 13 | |
| 0.1.40 | 6 / 13 | |
| 0.1.39 | 6 / 13 | |
| 0.1.38 | 6 / 13 | |
| 0.1.36 | 6 / 13 | |
| 0.1.35 | 6 / 12 | |
| 0.1.33 | 6 / 12 | |
| 0.1.31 | 6 / 12 | |
| 0.1.30 | 7 / 13 | |
| 0.1.29 | 7 / 13 | |
| 0.1.28 | 7 / 13 | |
| 0.1.27 | 7 / 13 | |
| 0.1.26 | 7 / 13 | |
| 0.1.25 | 7 / 13 | |
| 0.1.24 | 7 / 13 | |
| 0.1.23 | 7 / 13 | |
| 0.1.22 | 7 / 13 | |
| 0.1.21 | 7 / 13 | |
| 0.1.20 | 7 / 13 | |
| 0.1.18 | 7 / 13 | |
| 0.1.17 | 7 / 7 | |
| 0.1.16 | 7 / 7 | |
| 0.1.15 | 7 / 7 | |
| 0.1.14 | 7 / 7 |
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.