@superbuilders/incept-renderer
QTI 3.0 Assessment Renderer - Parse, validate, and render QTI XML with customizable themes
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:@superbuilders/slog | AI (dependencies): First-party @superbuilders scoped dep, consistent with org's other packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is within same org; provenance shows known-maintainer manual publish. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @superbuilders/* packages; consistent with internal library factoring, not a supply-chain risk pattern. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to compound this. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.1.30 | 16 / 4 | |
| 0.1.29 | 16 / 4 | |
| 0.1.28 | 16 / 4 | |
| 0.1.27 | 16 / 4 | |
| 0.1.26 | 16 / 4 | |
| 0.1.25 | 16 / 4 | |
| 0.1.24 | 16 / 4 | |
| 0.1.23 | 16 / 4 | |
| 0.1.22 | 16 / 4 | |
| 0.1.21 | 16 / 4 | |
| 0.1.20 | 16 / 4 | |
| 0.1.19 | 16 / 4 | |
| 0.1.18 | 16 / 4 | |
| 0.1.17 | 16 / 4 | |
| 0.1.16 | 16 / 4 | |
| 0.1.15 | 16 / 4 | |
| 0.1.14 | 16 / 4 | |
| 0.1.13 | 16 / 4 | |
| 0.1.12 | 16 / 4 | |
| 0.1.11 | 16 / 4 | |
| 0.1.8 | 16 / 4 | |
| 0.1.7 | 16 / 4 | |
| 0.1.5 | 16 / 4 | |
| 0.1.4 | 16 / 4 | |
| 0.1.3 | 16 / 4 | |
| 0.1.2 | 16 / 4 | |
| 0.1.0 | 14 / 4 |
v0.1.30
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ameeralns) than the most recent previously approved version (supersterling) on 2026-07-13, but ameeralns is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.