@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 — the axios compromise (March 2026) relied on exactly this gap.
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.