symbol.prototype.description MIT 9 versions

symbol.prototype.description

npm Repository Homepage

Spec-compliant shim for Symbol.prototype.description proposal.

9

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ljharb

Keywords

polyfillshimesshimecmascriptsymboldescription

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New deps gopd and es-object-atoms are standard ljharb/es-shims utilities, consistent with this package's ecosystem and authorship. Not a supply-chain risk.	ai	2026/04/24
dependencies	unvetted-dep:gopd	AI (dependencies): gopd is a standard es-shims/ljharb utility for property descriptor access; its use is appropriate and expected in this polyfill package.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): ljharb is a highly trusted publisher; dormancy on a stable polyfill package is expected and not indicative of account takeover.	ai	2026/04/23

Versions (showing 9 of 9)

Version	Deps	Published
2.0.0	7 / 23	2025-12-11
1.0.7	7 / 14	2024-12-18
1.0.6	5 / 14	2024-02-15
1.0.5	4 / 10	2021-08-17
1.0.4	4 / 10	2021-02-21
1.0.3	4 / 10	2020-11-23
1.0.2	2 / 6	2019-12-14
1.0.1	2 / 6	2019-10-19
1.0.0	1 / 5	2018-01-23

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

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.