← Home

@prairielearn/browser-utils

npm Repository

Helpful utilities for writing client-side vanilla JavaScript.

34
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

nwalters512mwest1066

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Monorepo CI publish quirk, no behavior change, provenance otherwise intact. ai
maintainer-change maintainer-removed AI (maintainer-change): Org-managed package publishing via GitHub Actions, not a takeover indicator. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; stable for this org's packages. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects CI/CD migration, not account takeover; SLSA attestation confirms legitimate publish. ai
dependencies unvetted-dep:@prairielearn/html AI (dependencies): Same-org sibling package from PrairieLearn monorepo; stable false positive for this package. ai

Versions (showing 34 of 34)

Version Deps Published
2.7.3 3 / 2
2.7.2 3 / 3
2.7.1 3 / 3
2.7.0 3 / 3
2.6.3 3 / 3
2.6.2 3 / 3
2.6.1 3 / 3
2.6.0 3 / 2
2.5.1 3 / 2
2.5.0 3 / 2
2.4.0 3 / 2
2.3.0 2 / 2
2.2.14 2 / 2
2.2.13 2 / 2
2.2.12 2 / 2
2.2.11 2 / 2
2.2.10 2 / 2
2.2.9 2 / 2
2.2.8 2 / 2
2.2.7 2 / 2
2.2.6 2 / 2
2.2.5 2 / 2
2.2.4 2 / 2
2.2.3 2 / 2
2.2.2 2 / 2
2.2.1 2 / 2
2.2.0 2 / 2
2.1.3 2 / 2
2.1.2 2 / 2
2.1.1 2 / 2
2.1.0 2 / 2
2.0.2 2 / 2
2.0.1 2 / 2
2.0.0 2 / 2

v2.7.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.2.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.