@ndla/preset-panda
Panda preset for NDLA.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): NDLA org internal maintainer rotation; consistent with known publishing pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org rotation; no takeover indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Both new deps are first-party (@ndla/core) and ecosystem-standard (@pandacss/dev) for a Panda CSS preset package. | ai | |
| dependencies | unvetted-dep:@ndla/core | AI (dependencies): Sibling package in the same NDLA monorepo; stable false positive for this package. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 0.0.78 | 2 / 0 | |
| 0.0.76 | 2 / 0 | |
| 0.0.75 | 2 / 0 | |
| 0.0.74 | 2 / 0 | |
| 0.0.72 | 2 / 0 | |
| 0.0.71 | 2 / 0 | |
| 0.0.70 | 2 / 0 | |
| 0.0.69 | 2 / 0 | |
| 0.0.68 | 2 / 0 | |
| 0.0.65 | 2 / 0 | |
| 0.0.64 | 2 / 0 | |
| 0.0.62 | 2 / 0 | |
| 0.0.61 | 2 / 0 | |
| 0.0.60 | 2 / 0 | |
| 0.0.58 | 2 / 0 | |
| 0.0.57 | 2 / 0 | |
| 0.0.56 | 2 / 0 | |
| 0.0.54 | 0 / 2 | |
| 0.0.53 | 0 / 2 | |
| 0.0.52 | 0 / 2 | |
| 0.0.51 | 0 / 2 | |
| 0.0.50 | 0 / 2 | |
| 0.0.49 | 0 / 2 | |
| 0.0.48 | 0 / 2 | |
| 0.0.47 | 0 / 2 | |
| 0.0.46 | 0 / 2 | |
| 0.0.45 | 0 / 2 | |
| 0.0.44 | 0 / 2 | |
| 0.0.43 | 0 / 2 | |
| 0.0.42 | 0 / 2 | |
| 0.0.41 | 0 / 2 | |
| 0.0.40 | 0 / 2 | |
| 0.0.39 | 0 / 2 | |
| 0.0.38 | 0 / 2 | |
| 0.0.37 | 0 / 2 | |
| 0.0.36 | 0 / 2 | |
| 0.0.35 | 0 / 2 | |
| 0.0.34 | 0 / 2 | |
| 0.0.33 | 0 / 2 | |
| 0.0.32 | 0 / 2 | |
| 0.0.31 | 0 / 2 | |
| 0.0.30 | 0 / 2 | |
| 0.0.29 | 0 / 2 | |
| 0.0.28 | 0 / 2 | |
| 0.0.27 | 0 / 2 | |
| 0.0.26 | 0 / 2 | |
| 0.0.25 | 0 / 2 | |
| 0.0.24 | 0 / 2 | |
| 0.0.23 | 0 / 2 | |
| 0.0.22 | 0 / 2 | |
| 0.0.21 | 0 / 2 | |
| 0.0.20 | 0 / 2 | |
| 0.0.19 | 0 / 2 | |
| 0.0.18 | 0 / 1 | |
| 0.0.17 | 0 / 1 | |
| 0.0.16 | 0 / 1 | |
| 0.0.15 | 0 / 1 | |
| 0.0.14 | 0 / 1 | |
| 0.0.13 | 0 / 1 | |
| 0.0.12 | 0 / 1 | |
| 0.0.11 | 0 / 1 | |
| 0.0.10 | 0 / 1 | |
| 0.0.9 | 0 / 1 | |
| 0.0.8 | 0 / 1 | |
| 0.0.6 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.4 | 0 / 1 | |
| 0.0.3 | 0 / 1 | |
| 0.0.2 | 0 / 1 | |
| 0.0.1 | 0 / 1 |
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonasc-knowit) than the most recent previously approved version (katrinewi) on 2024-11-08, but jonasc-knowit 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.0.42
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (katrinewi) than the most recent previously approved version (jonasc-knowit) on 2024-11-08, but katrinewi 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.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonasc-knowit) than the most recent previously approved version (katrinewi) on 2024-07-30, but jonasc-knowit 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.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (katrinewi) than the most recent previously approved version (jonasc-knowit) on 2024-07-30, but katrinewi 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.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonasc-knowit) than the most recent previously approved version (gunnarvelle) on 2024-06-29, but jonasc-knowit 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.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.