gettodaysdate 1.0.8 → 1.0.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +24 -1
  2. package/index.js +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,13 +1,36 @@
1
1
  # gettodaysdate
2
2
 
3
+ [![npm version](https://img.shields.io/npm/v/gettodaysdate)](https://www.npmjs.com/package/gettodaysdate)
4
+ [![npm downloads](https://img.shields.io/npm/dm/gettodaysdate)](https://www.npmjs.com/package/gettodaysdate)
5
+ [![license](https://img.shields.io/npm/l/gettodaysdate)](./LICENSE)
6
+ [![published by puppeteer + a custom passkey](https://github.com/nmpwaifu/gettodaysdate/actions/workflows/publish.yml/badge.svg)](https://github.com/nmpwaifu/gettodaysdate/actions/workflows/publish.yml)
7
+
3
8
  Returns a fixed ISO date.
4
9
 
5
10
  ```js
6
11
  const { getTodaysDate } = require('gettodaysdate');
7
12
 
8
- getTodaysDate(); // '2026-09-01'
13
+ getTodaysDate(); // '2026-09-04'
9
14
  ```
10
15
 
16
+ # Why?
17
+
18
+ This is a PoC and a middle finger to NPM's change to force passkeys for publishing on everyone, because they think their users are too dumb.
19
+
20
+ Sure, there have been supply chain attacks, yeah tokens got leaked, whatever. That's the users fault. I mean you guys already blocked scripts and git etc. by default on npm 12, but forcing either passkeys or OIDC on a few providers is dumb.
21
+
22
+ Well, I will use my own passkeys, via keys I generate with OpenSSL! And guess what, since I can set the credentialId to any 32 bytes I want, I will have some fun with it:
23
+
24
+ <img width="1280" alt="Custom credentialId for passkeys I register via shim" src="https://github.com/user-attachments/assets/41c35340-54a4-4201-9598-bd826ded2546" />
25
+
26
+ ## How?
27
+
28
+ Review the [SETUP.md](./SETUP.md) doc on how to register a custom passkey via a shim, and the [release](./.release/) folder for how the publishing works via puppeteer + custom passkeys
29
+
30
+ ## AI Use
31
+
32
+ This was primarily done via some human webauthn research, and then prompting an LLM to help write shims, docs and the rest.
33
+
11
34
  ## License
12
35
 
13
36
  WTFPL
package/index.js CHANGED
@@ -1,7 +1,7 @@
1
1
  'use strict';
2
2
 
3
3
  function getTodaysDate() {
4
- return '2026-09-01';
4
+ return '2026-09-04';
5
5
  }
6
6
 
7
7
  module.exports = { getTodaysDate };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "gettodaysdate",
3
- "version": "1.0.8",
3
+ "version": "1.0.10",
4
4
  "description": "Return a fixed ISO date.",
5
5
  "main": "index.js",
6
6
  "exports": {