@coursebuilder/next
Next for Course Builder.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@coursebuilder/server | AI (dependencies): First-party monorepo sibling package, same publisher/scope. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds first-party sibling dep, not an external supply-chain risk. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped @coursebuilder package; not a typosquat of nuxt — different namespace and purpose. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @coursebuilder package; Levenshtein match to jest is coincidental. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped @coursebuilder package; Levenshtein match to knex is coincidental. | ai | |
| phantom-deps | phantom-dep:inngest | AI (phantom-deps): inngest is a declared runtime dependency in package.json; phantom-dep heuristic misfired. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.0.36 | 3 / 4 | |
| 0.0.35 | 2 / 4 | |
| 0.0.34 | 2 / 4 | |
| 0.0.33 | 2 / 4 | |
| 0.0.31 | 2 / 4 | |
| 0.0.28 | 2 / 4 | |
| 0.0.27 | 2 / 4 | |
| 0.0.26 | 2 / 4 | |
| 0.0.25 | 2 / 4 | |
| 0.0.24 | 2 / 4 | |
| 0.0.23 | 2 / 4 | |
| 0.0.22 | 2 / 4 | |
| 0.0.21 | 2 / 4 | |
| 0.0.20 | 2 / 4 | |
| 0.0.19 | 2 / 4 | |
| 0.0.18 | 2 / 4 | |
| 0.0.17 | 2 / 4 | |
| 0.0.16 | 2 / 4 | |
| 0.0.15 | 2 / 4 |
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.