← Home

@glint/template

npm Repository Homepage
24
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

wagenethm_krystankatiegenglernullvoxpopuli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package now publishes via GitHub Actions CI with SLSA attestation; this is the expected publisher going forward. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are part of a documented team transition on a well-established Ember/Glimmer tooling package. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers correspond to the same team transition; no malicious indicators present. ai
bogus-package bogus-package AI (bogus-package): Type-definitions-only package; sparse README and no keywords are expected for this kind of internal tooling package. ai

Versions (showing 24 of 24)

Version Deps Published
1.7.8 0 / 10
1.7.7 0 / 10
1.7.6 0 / 10
1.7.5 0 / 10
1.7.4 0 / 10
1.7.3 0 / 10
1.7.2 0 / 10
1.7.1 0 / 10
1.7.0 0 / 10
1.6.2 0 / 10
1.6.1 0 / 10
1.6.0 0 / 10
1.5.2 0 / 5
1.5.1 0 / 5
1.5.0 0 / 5
1.4.0 0 / 5
1.3.0 0 / 5
1.2.2 0 / 5
1.2.1 0 / 5
1.2.0 0 / 5
1.1.0 0 / 5
1.0.2 0 / 5
1.0.1 0 / 5
1.0.0 0 / 5

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.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.

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dfreeman → wagenet (on 2024-01-05, known maintainer) provenance

This version was published by a different npm account (wagenet) than the most recent previously approved version (dfreeman) on 2024-01-05, but wagenet 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.

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chriskrycho → dfreeman (on 2023-09-25, known maintainer) provenance

This version was published by a different npm account (dfreeman) than the most recent previously approved version (chriskrycho) on 2023-09-25, but dfreeman 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.

v1.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dfreeman → chriskrycho (on 2023-08-17, known maintainer) provenance

This version was published by a different npm account (chriskrycho) than the most recent previously approved version (dfreeman) on 2023-08-17, but chriskrycho 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.

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.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.